Hi there,
I am looking for a solution to have project related variables which I can use for workflow conditions.
Context = I provide Jira to different dev teams and projects. Until now, I was able to have two "standard" workflows for stories and bugs which fit everybody's need. Some of these teams and projects introduced an additional staging system to their DTAP street (e.g., Test, QA, Production). The workflow should align to these three steps and supports the collaboration of dev teams and tester by clarifying the responsibility.
It was easy to add new statuses which represent the responsibilities and can be used on Kanban boards. But here is the tricky part: Many teams and projects are using stories and bug, but only few have different DTAP instances so not every status is relevant for everybody. The workflow should be flexible and respect project internal policies at the same time. How can I
I don't want to work with several forks of the story and bug workflows. Over time, these workflows grow to 17 statuses and 50 transitions. Working with project categories may work today. But I doubt that this solves future requirements.
Do you have any idea how to manage this?
Cheers,
Bernd
Hi @Brüse_ Bernhard ,
while this might not be doable out of the box, if evaluating an additional app is applicable for you, I'd like to suggest having a look at Jira Workflow Toolbox (https://marketplace.atlassian.com/apps/29496/jira-workflow-toolbox?hosting=server&tab=overview).
Its built-in project properties should help with your use case since they're intentended to provide the exact functionality you're describing. See a short introduction into project properties in the related documentation here: https://marketplace.atlassian.com/apps/29496/jira-workflow-toolbox?hosting=server&tab=overview
Cheers
Thorsten
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.