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

Approve a ticket before Development

Joao Borges_ch4uwn

Hi there,

How could I implement some restrictions on a a specific issue type in JIRA.Current project has 8 different issue types

Example:

I just created an issue type called Infrastructure. If a issue type = Infrastructure, in order to move from "Review" column to " TO DO", I need to add a restriction to assign a ticket to a specific person for approval

Once this person approves it, then ticket is good to go to TO DO column

Thanks

Accepted answers

John Funk

Hi Joao,

This is the kind of thing that JSM really helps with. It has built in approval functions that do exactly what you are wanting to do. I would suggest you give it a try, although it will mean a possible extra expense.

All comments

Jack Brickey

First just an observation/opinion. It seems a bit heavy to have an issuetype for use here vs. say using Components. Admittedly I don't understand your needs. :-)

But given you are using issuetype here is what I suggest...

Create a unique workflow (hopefully Classic here) for Infrastructure issuetype. on the Create transition add a PF to assign to a specific person. Create a custom field for Approved (yes/no, default to no). Once the approver sets to approved then a Validator on the transition to To Do will allow the transition.

Joao Borges_ch4uwn

@Jack Brickey I was trying to do by components but was not able to. Could I add a transition for a specific component ?

Joao Borges_ch4uwn

@ACK, also I had issues in the past with custom field, that affected the whole project and other people were unable to create tickets,

Jack Brickey

Not exactly and it may be that (understanding your use case better here) the separate issuetype is the way to go. When I say "infrastructure" it made me think that you might use components to capture your SW areas (Infrastructure, UI, Backend, etc.) which works well in that you can assign component leads and these leads would approve changes. But if indeed only Infrastructure requires approval then maybe issuetype is the way to go.

Now, what you could do using Components (maybe as their used to be a bug and unsure if addressed) is to have two different paths w/in the workflow. One that goes straight to To Do (doesn't require approval) and another that must first go thru Approval status before To Do. The transition directly to To Do is allowed if the Component is not Infrastructure (use Condition Value Field I think) whereas Infrastructure issues must go thru Approval status first.

John Funk

Hi Joao,

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud