[#897] - Add issue templates

[EdgarRamirezFuentes]

Resolve #897 by adding bug report, documentation related, enhancement request, feature request, and question issue templates.

Following this checklist to help us incorporate your contribution quickly and easily:

• Make sure there is a GitHub issue filed
  for the change (usually before you start working on it). Trivial changes like typos do not
  require a GitHub issue. Your pull request should address just this issue, without pulling in other changes.
• Each commit in the pull request should have a meaningful subject line and body.
• Format the pull request title like [#XXX] - Fixes bug in SessionManager,
  where you replace #XXX with the appropriate GitHub issue. Best practice
  is to use the GitHub issue title in the pull request title and in the first line of the commit message.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• add fixes #XXX if merging the PR should close a related issue.
• Run mvn clean install apache-rat:check to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
• If you have a group of commits related to the same change, please squash your commits into one and force push your branch using git rebase -i.

Trivial changes like typos do not require a GitHub issue (javadoc, comments...).
In this case, just format the pull request title like [DOC] - Add javadoc in SessionManager.

If this is your first contribution, you have to read the Contribution Guidelines

If your pull request is about ~20 lines of code you don't need to sign an Individual Contributor License Agreement
if you are unsure please ask on the developers list.

To make clear that you license your contribution under the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

• I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
• In any other case, please file an Apache Individual Contributor License Agreement.

[lprimak]

Im inclined to approve this.
However, since I don't really have any expertise in setting these up,
can somebody else take a look as well :)

[fpapon]

Just a little comment about the version list in the bug report template, otherwise LGTM.
@EdgarRamirezFuentes Thank you for your contribution!

[fpapon]

I'm not sure this is a good idea to provide a version list because we will need to maintain it up to date.
May be a simple input text field should be enough.

[EdgarRamirezFuentes]

Understood!
I made the changes in the bug report file, and switched the Shiro version to a textarea. 😄

[fpapon]

LGTM!

[fpapon]

@bmarwell is it ok with what you had in mind?

[bmarwell]

I think we can omit the environment b/c Java.

[bmarwell]

Maybe replace with a text field for application server, Java version, etc

[lprimak]

i.e Environment? :)

[EdgarRamirezFuentes]

You mean something like this?

[bmarwell]

"what was the actual outcome"

[bmarwell]

It's missing "what did you expect instead"

[EdgarRamirezFuentes]

So, I change the label to "what was the actual outcome" instead of "What happened", and add a new textarea with the label "what did you expect instead"?

[bmarwell]

This is not required imho. Or maybe rephrase it? @bdemers might want to suggest something?

[bmarwell]

@bmarwell is it ok with what you had in mind?

It's a great start!

[lprimak]

I would say to merge this "as is" and then update it when we figure out what the exact copy should read.
WDYT?

[EdgarRamirezFuentes]

@lprimak
I could commit the modifications I made in the environment field, and It could be merged and modified later as you mentioned.

[lprimak]

@bmarwell What do you think?

[bmarwell]

Yes, please change accordingly.

[EdgarRamirezFuentes]

Done!
I modified the environment field to be a text field, and added the fields to explain what was the actual and expected outcome.

[bmarwell]

Yup, that's a start!

[fpapon]

@EdgarRamirezFuentes thanks for your first contribution!