we have a User story which is getting deployed.
Want to create a sprint and Release, but I find that it is already marked as part of some other sprint and release in Jira.
Can we still go ahead and create a new sprint and release and assign this user story to the new sprint and release, in Jira?
You can put an issue into two sprints, but remember that this will break it for the team that does not deliver it completely.
Generally, you shouldn't do this - there's two separate pieces of work to do here, with two different teams, so there should really be two stories.
There is one exception to this above I would say. if both teams work on exactly the same sprint cycle at all times it should be fine.
But the way to make this work properly is a lot more work and less likely to work long term then implementing it correctly in the first place and having two pieces of work that talk to one another
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Recommended Learning For You
Level up your skills with Atlassian learning
Jira Align Program Essentials
Learn how to use Jira Align at the program level and how to plan for and manage your Program Increment (PI).
Managing Agile Boards and Reports
Learn how to pick the right board type for your team and customize it to fit your specific requirements.
Atlassian Certified Associate
Jira Software Board Configuration
Earn an associate-level credential from Atlassian that shows you can effectively configure Jira Software boards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.