Can the workflow properties be limited to an issue type?

[Suresh]

Can the workflow properties https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/ be applicable for a specific issue type? For example, if a workflow is shared by two issue types - Epic and Story, can I make them applicable for only Epic but Not on Stories?

[Walter Buggenhout]

Hi @Suresh Mantrala, no. They are workflow properties. But the workaround is fairly simple: copy your workflow and make separate versions for each issue type. Then you can specify the properties you like in each workflow separately.

Hope this helps!

[Kelly Arrey]

Then add the new workflow to the workflow scheme for the project to associate it with the relevant issue type.

[Suresh]

Seperation of workflows for each issue type is already known and Not pursued at this time. Wanted to know, if Atlassian has any issuetype based Workflow permission properties. Looks like the answer is NO.

[Walter Buggenhout]

Indeed, @Suresh Mantrala.  

[Danno]

@Walter Buggenhout I thought I understodd your recomended approach but I'm either implementing it wrong or don't understand how or where to use the property.

I created two separate workflows and tried using this property on the first transition from create to the first Status to limit who could create the issue to a role.

Permission: jira.permission.create.projectrole  Value: <projectroleID>

It isn't working correctly since it allows someone to create the issues. Do I need to add the overall create.denied property as well?

[Kelly Arrey]

If you want to enforce "Conditions" or "Validators" on a workflow transition, use Workflow "Conditions" and "Validators", not "Properties". See Configure Advanced Issue Workflows.

[Danno]

@Kelly Arrey, thank you for the reply, but unfortunately, that won't work for what I was trying to do. The project's create permission has to be open for the workflow associated with one of the issue types. I'm trying to enforce the creation of the second issue type to a set of users by project role. I'm trying to keep from breaking the existing project into two projects.

Add-ons are out of the question right now.

[Kelly Arrey]

Hi @Danno, my apologies, I thought we could add a condition to the Create transition but the Create transition apparently doesn't support that.

[Danno]

@Kelly Arrey indeed, one of the many things with this tool that can be quite annoying. 🙄