Forums

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

Automation rule comparing times is triggering when it shouldn't

Jeffrey Bistrong
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.
November 15, 2023

We have a process that is supposed to begin at a certain time (3 PM).

 

When it hits 45 minutes before the task is supposed to begin its supposed to transition it from Backlog --> On Deck

 

When it hits 5 minutes before it is supposed to transition it from On Deck --> Ready to begin. 

 

However both of these rules do not work the way it is supposed to.

 

We have a custom field called start time, its a free text field. 

 

First if statement

{{now.convertToTimeZone("America/Los_Angeles").plusMinutes(45).shortTime}}

greater than

{{issue.customfield_11976.todate("HH:mm:ss").shorttime}} (this is the start time field)

 

Then it is supposed to transition it only if its within 45 minutes of the start time, but it always transitions it no matter whatMonosnap Automation - Jira 2023-11-15 10-16-01.pngMonosnap Automation - Jira 2023-11-15 10-15-25.pngMonosnap [RRNC-2974] test - Jira 2023-11-15 10-17-23.png

 

 

 

 

4 answers

1 accepted

0 votes
Answer accepted
Mirek
Community Champion
November 9, 2018

— nobody of them will see other projects / issues / users etc

It depends on your other project permissions. If admins in other project would add a group or individual user to the project they would see it. You do not have much control on that.

— project lead will be the only assignable user

There is a permission Assignable User so you need to modify your Permission Scheme and add only Project Lead to this permission

— managers will see only theirs issues in this project (e.g. I am manager1, and I don't see issues created by manager2)

This is done via Security Levels. You need to define a default security level that would include Reporter (or a user fields that define Managers if someone is filling the ticket not managers)

ML888
November 9, 2018

Thanks! Well the questions is about configuring Security Leveles. Do you have a specific example? 

Mirek
Community Champion
November 9, 2018

— managers will see only theirs issues in this project (e.g. I am manager1, and I don't see issues created by manager2)

If I am a manager and I create a ticket (that should be only visible to me) then I become the Creator/Reporter of this issue. So if you define a default Security Level called for example "Restricted" and add only Reporter to it then people would only see what they created until the Reporter would change or Security Level of this specific issue..

ML888
November 9, 2018

Yes! Finally works, thank you! 

Like Mirek likes this
0 votes
kavi shree
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.
November 9, 2018

HI @ML888

 

I would suggest the following steps for your requirement.

 

nobody of them will see other projects / issues / users etc

1.Set the roles on who to access the project

2.Set the browse project permission to those Project roles only

eg:

Add the users to Admin role to those who need to access Project admin part

Add the users to user role to those who need to have access only to work with issues not the project admin part(Create a user role to provide basic project permissions)

 

project lead will be the only assignable user

 

1.Set default assignee has project lead

 Project  setting->users and roles->Edit default->default assignee to project-lead

2.Go to permission scheme->set Browse project and Assign Issues to the project lead

 

managers will see only theirs issues in this project

Set a Issue security scheme which is restricted only to reporter (if only managers use to create issues)

Or

1.Create a user picker field

2.Set a Issue security scheme which is restricted only to the user picker field(if any one can created issue but only respective mangers should view the issue)

 

Can use the field(user picker)to choose the manager name.

 

Note:

To get all this work the basic permission could be "Browse project" and "Create Issue(in 1st and 2nd case)"

 

Cheers,

Kavishree K

0 votes
PADMA KOTHAKOTA
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.
November 9, 2018

Hi,

I think below answers will suit your requirement

-->If you don't want others to see your projects / issues . you can restrict the Browser project permission to Project roles .. so who has project permission can see the project.

--If project lead want to have only assignable permission then project lead  should have assignable user permission ,&browse project and you can remove project lead from other permissions. If any security level is applied to the issues he cannot see .

-->you can use issue security scheme and set the security level only to  reporter. so if they select this security level only reporters can see the issues others cannot .

0 votes
ML888
November 9, 2018

The main point is about hiding issues which were created by another manager from other managers. I know how resolve #1 & #2 from my list

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events