Jira automation rules on requiring time estimates and logs

[YoursTrully]

Hi,

I'm new in Jira. I just want to learn how to set up automation for the following:

- When a ticket is created, the original estimate must be set
- When a ticket is moved from in progress to somewhere else, work time needs to be logged
- If the ticket moves to a column right of in progress, the remaining estimate needs to be 0

Thanks in advance for your help!

[Jack Brickey · Accepted solution]

Hi Arvie, welcome to the Community. For these requirements you wouldn’t need Automation. Rather you would use validators in the workflow along with screens.

• for the create you could create a unique screen that has the OE field included. Update the Create transition with a Validator of Field required for the OE and add the newly created screen to the transition
• for the time logging you can repeat the above for the appropriate transitions  using the Time Spent field.
• for the remaining time what I like to do is set it to zero when the issue transitions to Done status.

please let me know if this is unclear or you get stuck updating the workflow.

[YoursTrully]

Jack! These are all the things I needed. Thanks for all your help!

[MB]

Hi Jack,

Can you please expand on this solution.  I currently would like to have the log work field automated as well.  I am not clear on how this is achieved by the workflow and unique screen that you mentioned to Arvie.  Can you please tell me how to get the desired result?

Thnaks

-M

[Jack Brickey]

@MB, this might be a different question TBH. When you say you want "the log work field automated", what exactly are you trying to do? Are you saying that you want to require the user to log work when transitioning the issue from one status to another status or something else.

[Sara Nicholson]

Hi @Jack Brickey 

I have a similar issue however, we have automation in place that, when the linked development project ticket status updates, the automation rule will update our service desk tickets to the matching status unless they are in a number of specific statuses ("In Progress" being one of them).

I originally set up my workflow to allow "All" statuses to transition into our dev statuses (unless they are in a handful of specific statuses like in progress) and added another transition with a validator, when going from "In Progress" to any of the development statuses, it would require the log work screen to be completed, thinking that since the transition only applied to the tickets if they are "In Progress," it wouldn't affect the other transition rule... This worked perfectly when manually changing statuses...However, once I added the automation to update a service desk ticket status when the development project ticket status changed, my workflow rules caused that automation to fail. 

Is there any way I can require the log work screen ONLY when a ticket is in In Progress and moves to any status without breaking my workflow or the automation I need the system to perform? Perhaps a post function or? I know there is a "New Action" automation to log work but it makes me set a time value that gets applied to the ticket. I need our agents to be able to document the actual time they spend on a ticket and somehow I would like it to be a required screen when they are setting the ticket status when leaving "In Progress," which is the last thing they do when leaving a ticket. 

Any help would be appreciated! :) 

Sara

[Jack Brickey]

Hi @Sara Nicholson , while it would be best to post as new question, since it would get more eyes on it, here is on thought I have.

how about creating another transition specifically for Automation without the Validator? You could restrict the transition to the automation 'user'.

[Sara Nicholson]

Thanks @Jack Brickey ! I reposted the question here. 

Sara