nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation Condition for project.projectTypeKey

Luc Trepanier

I would like a rule to execute only if the issue is part of a Service Management project. I found that the smart value project.projectTypeKey should allow that.

But when I implement the condition:

{{issue.project.projectTypeKey}} equals "Service management"

it fails all the time.

I do not want the rule to execute for issues for Jira Software...

Thank you for your help.

Accepted answers

Mark Segall

Hi @Luc Trepanier - I ran into this same issue as well. projectTypeKey actually stores Service Management projects as service-desk. Here's the full list:

Jira Software: software
Jira Service Management: service-desk
Jira Work Management: business

All comments

Mark Segall

Hi @Luc Trepanier - I ran into this same issue as well. projectTypeKey actually stores Service Management projects as service-desk. Here's the full list:

Jira Software: software
Jira Service Management: service-desk
Jira Work Management: business

Luc Trepanier

Thank you, Mark!

John Isherwood

Hi @Mark Segall thanks for supplying the values. However, I'm not sure if Atlassian have changed them, but I discovered that Jira Service Management = service_desk (with the underscore) when I checked the log action for an automation using {{project.projectTypeKey}}

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

automation

smart-value

jira-service-management-cloud

project-key

jira-service-management