I have more of a software engineering question in regards to JIRA.
I find that Atlassian JIRA has "resolution" field and it can be as invalid.
Sometimes bad practices use these without any reason and that leads to many open questions.
Is there any way more details broad category of "invalid" sub states be defined?
Please help if you have experienced this and what can be better ???
I came up with below sub-states, so test and developer can work in harmony --
INVALID - USER ERROR
instances, where the user has totally goofed up in sending the command itself
INVALID - SETUP ERROR
user commands are good, but the setup is totally in a bad state
INVALID - CONFIG ERROR.
user is good, setup is good, but the feature configuration is totally messed up
INVALID - FEATURE LIMITATION
user is good, setup is good, but the feature configuration is good, but there is known issue or limitation
INVALID - OTHER DETAILED REASON
Something the developer/tester needs to agree upon.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events