These sound like different issue types to me.
Representing them in the workflow feels like nonsense - what would be the point of having an item that has status like "bug", "nice to have" and being able to swap between them as part of the workflow?
Having different fields and workflows for the different issue types really does work well though, and setting up something where customers/end-users raise "issues" in one project (without firmly pre-judging what they are because customers often don't know whether it's a bug, a new feature or something else) and having a process where your developers/product-teams triage them over into another project (changing the issue type to the right one on the way)
We have a transition and state that is Backlogged or you can use something like Scheduled if you are going to work on it right away. Basically, we will move these enhancement or bug requests to a backlogged state and unresolved and then once they are pulled into a version for a release, then they are moved in to a started or in progress state. We have some other states while in backlog such as ready for grooming (all requirements and criteria defined) and groomed (means it has been story pointed or estimated and ready to pull into a version/sprint).
We never resolve them unless they are done, we never plan to fix, or they are a duplicate.
@ isobretatel: do you think resolving them as "Won't fix" is the right way ? In our Jira, "Won't fix" means, that the issue will never be fixed, not in the next release and not in any future releases.
If we don't know, when an issue will be fixed, we do not resolve it.
It does sound like your resolutions aren't being used in a good way. If something is resolved-won't-fix, that really should mean "we are not going to work on this again, there's nothing we can/will do". If it's really going to get looked at for a later release, I don't think it should be resolved at all.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! My name is Amir and I’m on the Jira Service Desk product marketing team at Atlassian. Our team would love to understand how you’re leveraging our ecosystem for Jira Service Desk. Wha...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs