Is it possible to use workflow/status properties in Workflow schemes with more than one workflow?

[Hauke Bruno Wollentin]

Hi all,

I played around with the workflow properties, for instance `jira.permission.create.user` which seems to work if there is only one workflow in the projects workflow scheme.

But if I add another workflow to e.g. only restrict Epics, this doesn't work anymore.

Is this intended? Or a known bug maybe?

Thanks,
Hauke

For more context: Not all people in a project should be able to create and edit Epics, but they should see them

[Trudy Claspill]

Hello @Hauke Bruno Wollentin 

Welcome to the Atlassian community.

Workflow properties have to be set in each workflow to which you want them applied. You would need to set the same workflow properties in the workflow for Epics.

[Hauke Bruno Wollentin]

Hi Trudy,

This is what I did. The Epics workflows do have its properties set as well as the "default" workflow.

Or do you mean that all workflows in the scheme need to share the same logic? Like if want to enable people to create Epics, I need to disable them in the other workflow?

[Trudy Claspill]

If you have a workflow that applies only to specific issue type(s), the properties you set in that workflow will apply only to those types of issues.

The workflow that is set as the default will be applied to any issue type that does not have a specific workflow associated to it. In that case, the properties in the default workflow apply to all the issues not governed by a specific workflow.

You can have different property settings in each workflow.

Reviewing your original post:

I played around with the workflow properties, for instance `jira.permission.create.user` which seems to work if there is only one workflow in the projects workflow scheme.

But if I add another workflow to e.g. only restrict Epics, this doesn't work anymore.

Please clarify exactly what you mean by "this doesn't work anymore".

The way I understood your post is:

You have a default workflow that includes in it somewhere the property jira.permission.create.user. 

You created a second workflow. You did not include that property in the second workflow. You explicitly associated the second workflow to the Epic issue type.

In this case the functionality of the jira.permission.create.user property should be impacting only the issue types that use the default workflow - all issue types except Epics.