Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Code review without a pull request

Hi Community Members

I have a situation, wherein our organization wishes to implement the below scenario:

A developer working on a JIRA task cannot mark it as Dev Complete unless the code has been reviewed on Gerrit. (+2 done on code)

I was searching for ways how the workflow can be made to wait until the code review is complete and prevent the developer from changing JIRA status for In Dev to Dev Complete.

Do we have a way how we can achieve this.

 

Thanks

1 answer

@Munish Sharma 

There is a workaround through which you can achieve this.

First make the transition button disappear from jira. You can provide a condition in workflow which is always false (for your specific transition). 

So you have removed manual option for your workflow status transition and now you need to make code to initiate this transition on an event in your code repository

Now you can add workflow triggers to move your status to Dev Complete , you can choose Pull Request Merge or Review closed.

Please take a look at this documentation :

https://confluence.atlassian.com/adminjiracloud/configuring-workflow-triggers-776636696.html

When workflow transitions are automated with triggers, permissions around who can move the issue between states are ignored. Same with conditions and validators. But don't fret: conditions, validators, and permissions will still apply for that transition when it's executed manually.

 

Regards

Prakhar

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

193 views 6 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you