Managing multi stream & cross product dependency Bugs.

[RajaKumar Burra]

We have products and where we support 3-4 parallel stream and each support for will end for 4-6 years.

Currently we manage bugs in our home-grown tools like below.

Supporting Streams:

• Release Stream 1 – Support Ends 2027
• Release Stream 2 – Support Ends 2029
• Release Stream 3 – Support Ends 2030

When we found a bug and file in Stream 1, It will create Bugs and Bugs Tasks like below.

• Bug 1
  • Bug Task 1 for Stream 1
  • Bug Task 2 for Stream 2
  • Bug Task 3 for Stream 3
  • Bug Task 4 for cross Product if any other dependent products needs to beixed.

Bug1 is actual place holder and Fix versions and Sprints are tracked in Bug Tasks. Until all Tasks are not resolved, Bug1 remain open.

What are the recommendations to manage it in Jira.

I am considering below two options.

1. Create Work Item type as Bugs and Bug Tasks and manage same as above.
2. Create Work Item type as Bugs and use Sub tasks for multiple streams. I think Sub Tasks have limitations and can not create cross project/products tasks and manage it.

Any suggestions and recommendations?

[Valerie Knapp]

Hi @RajaKumar Burra , welcome to the Atlassian Community and thanks for your post.

I think it would make sense to create the Bugs as the Epic level. That way, if you need to, you can also have subtasks.

So, you could have

Bug (Epic)

- Bug Task for Stream 1 (Story level)

- Bug Task for Stream 2 (Story level)

- Bug Task for Stream 3 (Story level)

with still the possibility to drill down into your Stories if you need to further break down the work.

I hope this helps you.

Looking forward also to what others have to say.

Best wishes

[RajaKumar Burra]

@Valerie Knapp  Thank you for quick reply.

I am not worrying about managing Epics and Stories. I am worrying managing the customer Bugs.

Customer file a Bugs in Stream 1 and they expect it is fixed in the current stream which they are using.  Since Bug 1 fixed in Stream 1, these should be go to downstream as well.