Hi,
I don't see what is the problem here.
By definition, each issue can be part of only 1 sprint.
You say you have issue x in sprint 1.
Issue x is closed/completed, also sprint 1.
Now you have issue y (dowsn't matter if it related to issue x or not), you put it in new sprint 2.
Issue y and sprint 2 are both open till you finish your work and mark them both as complete (same process you did for issue x and sprint 1).
So what is the issue?
You want to connect between issue x and issue y, create a link between them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ishwinder Singh,
I think that issue X is actually completed in Sprint 1. Issue Y is a supplement to issue X. In this case, you can use the issue link function to associate X with Y. It is recommended that an issue not be repeated in different sprints. Because this is not in line with the principle of agile.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes i do agree. But the management is now asking for it. And how to follow the issue link function?
Please let me know a flow for it/ steps to link.
Thanks and Regards
Ishwinder Singh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ishwinder Singh,
Hope the following content will help you.
https://confluence.atlassian.com/jirasoftwareserver0710/linking-issues-953147181.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.