For the Defect issue type it have different transition state To Do/Open--Assign --Resolved--Closed Issue--Reopen Defect--Re-assign. This workflow is properly worked in Defect backlog project. But it doesn’t work when we use same workflow in release project after starting Sprint, once we planned the defect in the same sprint.
We are experiencing an issue with the Defect issue type. A Defect does not have the same states of stories and tasks so we have created a column mapping in our board to map the Resolved state of a defect to the “In Progress” state of the active sprints view.
However, the problem is that the representation of a Defect issue created within a System Release project does not seem to be consistent. When a Defect is set to the resolved state the issue key becomes strikeout. But it shouldn’t be cause its status is not mapped to Done. If the defect is re-opened (state is moved back to TODO) then the key becomes not strikeout. When the defect is re-assigned the key becomes strikeout yet the Defect is still in the In Progress state.
In the release project we have only three state To Do--In Progress--Done & we are creating board in the project. In column management added column as shown in screenshot1
Please find attached screenshots regarding Workflow for Defect Issue type for your reference; Screenshot2 & Screenshor3
Please let me know how to resolve this problem.
Thanks in Advance!
@Jack Graves first caught our eye with his incredible breakdown of what, in his opinion, can make or break a Jira software implementation. (Read his thoughts on this thread)! In this followup Sh...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot