Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Automation: copy custom value to "originalestimate"

Hello folks,

I want to copy a numeric customfield "customfield_11900" to the system field "timeoriginalestimate.

 

I was trying different ways an one for e.g.

2023-09-29 13_28_05-Automation - Multicloud Managed Services.png 

but this rule doesn't work

2023-09-29 13_28_05-Automation - Multicloud Managed Services 2.png 

I create the rule with smart values.

 

1 answer

0 votes
Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 08, 2023

Hi @DG 

You shouldn't need the Advanced section - this should work:

  • Trigger: ...
  • Action: Edit Issue
    • Field = Original Estimate (System)
      • Value = {{issue.customfield_11900}}

I'd also check that the user who is actioning the rule has the appropriate time tracking permissions.

Also, the estimate field will use whatever the default time tracking value is - eg. minutes. You could use smart values (maths expressions) though to get round this. For example, the default is hours but the numeric field is in minutes - so the smart value would be {{issue.customfield_11900.divide(60)}}

Ste

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events