In a situation, For a product but for two different Dev-platform I have created two different project. Since project requirement is not even bit different, so is there way to keep same set of story shared across project and this should be closed separately .
I have idea to put board-filter for already create project-stories so can keep same board to track multiple project status, but not mentioned above.
Assuming two different projects, two different assignees, two different deliverables, etc...
Clone the story and assign the clone to the other project. Good news is they will be linked automatically.
And yes, you can create a board to see both stories across both projects.
I should warn you that this approach comes with a price - you'll now have to maintain both stories with any changes to requirements, etc... as they are two different objects (not that that ever happens ).
Another solution solution is to put the info into an EPIC and define a story attached to it for each environment. Use the EPIC to define/hold common information and use the stories to hold information specific to a given implementation. This reduces the maintenance overhead.
Another approach I hesitate to mention but will, would be to create subtasks in the same story for each environment and assign them to the different teams (kind of a lower level implementation of the EPIC approach) - not the best solution as subtasks are limited compared to Stories...
Hope this is more helpful than confusing. Let me know how it works out for you.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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