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

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,821
Community Members
 
Community Events
176
Community Groups

Setting original Estimate with Automation

Dear all,

i'm having some trouble with setting the original estimate field's value using automation. In my scenario i have a parent ticket from one project that creates a ticket in another project, with the same values. 

When i searched the community questions, i found a post about someone who was able to do it by creating the ticket first, then updating the field. But when i tried that, the original estimate field value was not changed.

So to debug it, i first set the value of the field manually then i change it again with the value of the parent ticket. And the results are weird.

Here is my parent ticket with origInal estimate = 10weeks (it's in french in the screen)

Capture1.PNG

Here are my two rules in the automation process

First the manual value

Capture2.PNG

Then the parent's ticket value

Capture3.PNG

In the created ticket, i see this in the logs :

The manual setting worked (in green)

Then, there's a "Remaining Estimation" that goes from 0 to 0 in blue (no idea what happens there)

Finally, the automated setting that changes the value from 5 weeks to 0 (the value is 10 weeks in my initial ticket)

Capture4.PNG

Any idea why the value goes to 0 when it's supposed to be 10 weeks like the parent ticket ?

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events