The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 

how to make tickets be evaluated by a person before being published?

Omar Agramonte
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 31, 2022

how to make tickets be evaluated by a person before being published

2 answers

2 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

2 votes
Answer accepted
Mirek
Community Champion
January 31, 2022

I am quickly thinking about two options

Option 1

Create two projects, one for review process second for final publish and move the tickets after review is done (alternatively create an automation that would do it automatically)

Option 2

Create a ticket but set issue security level so that it would be visible only to the reviewer, then when the review is done change the security to a different level that would show the ticket.

Ste Wright
Community Champion
January 31, 2022

I concur with Option 2 - I think it'd be the best solution.

You could use Automation to change it to visible afterwards - for example, have a custom checkbox field - if it's checked "Yes" then it becomes visible.

The good thing about a custom field like this is it could be unchecked back to "No" if you need to hide it again, with another Automation rule to reverse the process.

Ste

Like • # people like this
Tim Perrault
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
February 1, 2022

The security level idea sounds really cool. I hope the user is on Cloud or they have Automation for their server/DC because you can do some really cool things. In fact since Automation is becoming a native feature to DC soon, I'm going to bookmark this idea.

 

Tim

Like • Mirek likes this
Omar Agramonte
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 1, 2022

some tutorial to create automation for the option one

Ste Wright
Community Champion
February 3, 2022

Hi @Omar Agramonte 

For Option 1, you'll need 2 separate Jira Projects.

Automation might then look like:

  • Trigger: Issue Transitioned - to Done
  • Action: Clone Issue - set to Approved Project, and clone everything else

Because there's no "Move Issue" Automation action, that's why I think Option 2 is preferable - this results in 2 Issues for each.

Ste

1 vote
Answer accepted
Tim Perrault
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
January 31, 2022

Hi @Omar Agramonte 

 

There are a couple of ways that I can think of doing this, but the one that just jumped out at me would be edit the workflow and add a new status something like "Review". Put this status in before your "close" status. Now when you transition to the Review status have a post function that automatically assigns it to the "Reviewer". Then on the transition from "Review" to "Close" add a validator that checks to make sure the user you want to transition the issue is in the assignee field.

 

Thanks,

Tim

TAGS
AUG Leaders

Atlassian Community Events