Using the Jira Release plugin in combination of BitBucket, there is the option in the report to display warnings for tickets not following the workflow, such as "Unreviewed code". In our case, we had a ticket and we committed some code into a feature branch for that ticket except during development of the ticket, we decided to kill off that feature and drop it. So we deleted the branch(including on BitBucket) and close the Jira ticket as "Won't Do"(GIT still has history of the commits). Except now the ticket shows up in the Unreviewed Code because there are dead end commits against the ticket and the ticket is "closed".
Is there a way to configure the warnings to not check tickets which are specific statuses, such as "Won't Do", etc?
I suppose we could try to rebase our GIT history or prune the "unwanted" commit and hope the Jira ticket will no longer have the commits. Then if that doesn't work, we'd have to create a fake pull request to a to-be-deleted branch to merge it into to satisfy the warnings.
To reproduce this:
1. Create a Jira ticket and add it to your board
2. Create feature branch for the ticket
3. Commit / Push code to remote against that ticket in a feature branch
4. Delete the branch on remote server (BitBucket)
5. Close the ticket as "Won't Do"
6. The warning will now be listed in the release reports
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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