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; } } }

Multiple status' for Create Issue transition

Danielle White

We are interested in having the status of newly created tickets default to particular status', based on the permissions of the user who entered it, for the same project.

For example, if someone who isn't part of the dev team submits an issue, we would like it to be assigned a status of 'Pitched'. And for tickets entered by anyone on the dev team, to be set to 'Approved' by default.

Is it possible to set conditions, based on permissions when creating new tickets? I haven't been able to find any documentation on this particular instance, but have seen lots on setting up conditions to limit possible workflows, once a ticket is created.

Accepted answers

All comments

Nic Brough -Adaptavist-

No. An issue type always follows one workflow, and all transitions have a fixed end point. So you can only have one "create" landing point. If you could get your dev team to raise one type of issue, and non-dev another, then you could di it by having different workflows for the different issue types.

If you were on Server, there are a couple of options that would let you check some conditions and immediately transition to the desired status.

Danielle White

I have this partially setup now.

I have two workflows for the project, one for the development team which includes Epics, Improvements, New Features and Stories. The other for marketing the marketing team which includes Bug and Pitch.

What I would like to do now, is limit the Marketing workflow to people in marketing and the Dev & Marketing workflow to people in the development group. Is that possible?

Nic Brough -Adaptavist-

Nope, sorry. If you can create an issue in the project, you have the rights to create one of any type in there.

There are some tricks you can play on Cloud, but they're ugly - essentially they'd let the user start creating the issue, they enter all the data and then get told they can't create it and they lose all the data.

Jordan M. Pflum

Hello Nic, you mention in your original response that "If you were on Server, there are a couple of options that would let you check some conditions and immediately transition to the desired status." Could you elaborate on this a little more - what these options entail? We may be looking for just such an outcome. Thanks!

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud