We are encountering a challenge in designing our development workflow, and I’d like to provide some background on the requirements. We have three product lines. The primary product line's development may involve tickets that affect multiple releases across various hardware models. However, the release and development timelines for these different hardware models may not align, sometimes resulting in months of separation.
Compounding this issue, two departments are employing different project management approaches: Agile and Waterfall. The primary product uses a Waterfall/V-model approach, and it’s important to note that fixes can sometimes be located in different folders or repositories due to legacy issues. Given this context, what workflows would you recommend for scenarios where the same requirement applies to multiple hardware models, particularly when source code commits are in different repositories and release dates differ? The development team has expressed a desire to avoid creating multiple tickets for the same requirement that applies to different fix versions, considering the challenges mentioned. I am also exploring opportunities to automate the workflow based on these conditions.
In contrast, the other two product lines are using an Agile approach and do not face the same issues when a single requirement needs to be applied to different versions. Looking for the community expert advise in JIRA to address our issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.