Can a user story be part of two jira sprints/Releases

[Chandrasekhar]

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?

[Nic Brough -Adaptavist-]

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.

[Clark Everson]

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