Forums

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

Pull request state

Hasmik Hovhannisyan
October 24, 2023

I'm trying to setup an automation to check the linked PR status and move the ticket back to the previous status if the PR is in "Draft" status. 

I've found some option in community but seems those are not working. 


I"m using smart value {{pullRequest.title}} and checking if that contains "Draft" and another option is I'm checking if {{pullRequest.state}} equals "Draft" and no success. Audit logs show that the issue didn't match the condition. 

Any ideas?

2 answers

0 votes
Joe Pitt
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.
October 26, 2018

The only reasonable option is to have 3 projects, one for each issue type and give the users access to those projects as needed. 

0 votes
Nic Brough -Adaptavist-
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.
October 26, 2018

To answer the question literally:  Rewrite Jira and add the code required to do permissions at lower levels.

Jira permissions are done only at a project level.  There's nothing to cascade down to.

You can do a little bit with issue security, but that only applies with "view", not the other 25ish permissions.

To do what you describe, you will need two things:

  • An issue security scheme with levels for each group saying "only that group can see issues in this level"
  • A listener that reads the components and sets the level appropriately

Suggest an answer

Log in or Sign up to answer