We are doing replacement stories of current stories being changed and need a good way to do it without just linking. Any ideas? So the first story once it gets to development we can not change it, so we write a new story and highlight the changes. It is getting crazy with four or more changes and hard to track.
Hi @Shelly Weber,
If I understand you well, there's 2 sides to your question:
In terms of process, it seems weird that you are still making changes to stories that have been committed to development. Unless it is the development team itself that is translating requirements into a task breakdown etc. For that purpose, we sometimes use the issue comments to communicate updates to a story.
Technically, it is possible that - from a certain workflow status - changes to the story are indeed blocked. This is done through the jira.issue.editable property associated with that workflow status.
A Jira administrator can modify this setting as described here.
We do replacement stories mainly for the ui and it gets crazy following links. I would love to have one story number even though it has had four changes (improvements) to it since the start of the story. We can not just change the main story AC as development puts in their information and we need to follow the flow for dev and testing...
Their is a time frame from when the story is first written to the priority of the improvement, so it may be months later before the devs get the story. This is for new development
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
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