Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

New Jira Tickets per release or one identical ticket with tagging each release

a_kim
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 25, 2022

Our team will have three product releases that have an identical user story.  We are discussing whether or not it would be best practice to recreate the user story/ticket once closed out for a release or to just use the same user story/ticket and tagging with each of the three products.  I look forward to the insights from this community.

1 answer

1 accepted

1 vote
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 25, 2022

Hi @a_kim -- Welcome to the Atlassian Community!

I doubt there is a "best practice" for this use case; instead what would align better with how your team works?

For example, does the capability built by the user story always, sometimes, or never get released simultaneously for the three products:

  • always: consider how to manage development for the three products and manage simultaneous release
  • sometimes: probably better to have separate work items (e.g. stories) as children of a parent (e.g. epic) and develop/release them as they progress
  • never: same as sometimes

Kind regards,
Bill

a_kim
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 26, 2022

This is very helpful.  Thank you!

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events