I have a custom workflow that we are using. The problem is that when I complete the Deploy transition on the workflow, instead of going to a Released state, the story goes to a Closed state which does not exist on my workflow. This happens for all issues of type story which are part of my custom workflow. Bug types don't see this but they are using the standard JIRA workflow schema.
I have attached 2 different screens shows. Showing the transition steps available for the story and the it's status, plus another showing the workflow that JIRA thinks it's applying. (based on the view workflow link).
This is a significant problem for our workflow and causes our product owner alot of problems.
It won't let me as I dont' have any karma points (beings this my first ticket). The actual support ticket that this is tied to does have the uploads.
Essentially, the workflow seems to be replacing one of my statuses for the "closed" status which then breaks most of my views that expect closed to not exist.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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