Approval

[Lena Sargsyan]

HI dear community,

How to add approvers/approval to my Jira workflow steps?

[Karyna Tyrnavska _SaaSJet]

Hi, @Lena Sargsyan !

If You`re ok with Jira add-ons, I suggest an alternative solution - Business Process Manager add-on.

It allows building single or multi-level approval workflow with conditions.

You can learn more about the BPM Approval feature via an article about vacation requests.

[Alex Koxaras _Relational_]

HI @Lena Sargsyan 

Approvals can be found only on JSM and not software. To setup approval you can read more here https://support.atlassian.com/jira-service-management-cloud/docs/set-up-approvals/

If you don't have JSM and you have software, then you can create manual approval, but they will not have the JSM functionality.

[Lena Sargsyan]

Thanks much  Alex for response.

I use software and manage a company managed project. And we don't have approvals in this case.

Now I am wandering if there is some other way (instead of setting approvals)  to serve the same logic. I just want to limit permissions of my team members in putting the issues done. Because very often we have the picture when someone sets an issue as done then the team lead or CTO says oh no it is not complete or didn't done properly, so I think there would be better to have two statuses from the category of done one of them will mean that the developer is done with his task the other one will indicate that the issue completion is approved and the process cycle is closed. And accordingly this second done (or completed or approved or finished) can be set only by a group of people.

Please help me out to skip this limitation of not having the approvals in software, and figure it out by other means.

[Alex Koxaras _Relational_]

A better approach would be to:

• Let the users move the issues to a status e.g. "Resolved". Resolve means that the user thinks that this issue has been resolved from his side.
• If the issue is resolved, then transition it to "Close" status.
• If the issue is not resolved, then move it back to the previous status

From the  above plan you let the users resolve issues (with the corresponding permission), but you grant the Close issue permissions to a handful of users.

You let your users know the difference between resolved and closed issue. Here's some references for you:

• https://community.atlassian.com/t5/Jira-Service-Management/what-is-the-difference-between-closed-and-resolved-status/qaq-p/882590
• https://community.atlassian.com/t5/Jira-Software-questions/What-is-the-difference-between-quot-closed-quot-and-quot/qaq-p/713495
• https://nulab.com/learn/software-development/resolved-vs-closed-whats-difference/#:~:text=Resolved%20means%20a%20developer%20fixed,the%20fix%20was%20done%20correctly.