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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Automation: Populating Original Estimate fields post issue creation

Hello,

I have a situation where I need to auto-populate the Original Estimate field with 0:15m instead of the standard 0:00m with after the issue is created.

 

When I have attempted to create this automation rule:

When -> Issue Created

Then -> Edit Issue

 Field -> there is no option to choose the Original Estimate field as it does not appear in the list of available options.

Is there a reason why certain fields like Reporter are unavailable from the dropdown?

Is there another process I could try to accomplish this use case?

Rod McWilliams

2 answers

Hi Rod,

Add the Time Tracking field in the appropriate screen like edit screen, it will have the Original Estimate and Remaining Estimate   

Hi @Ramaiah Pendli,

Thanks for the reply.

That's the confusing part to me.

I have the Time Tracking fields in all three screens (create, edit, view). We use Time Tracking across the board.

When I try to choose those fields from the Field option in the Edit issue, they do not appear. All the other fields identified in the Edit Screen (except for Reporter) are available. 

Neither Time Tracking nor the individual Original Estimate or Remaining Estimate are options. I don't know why. Is there a setting somewhere else that is rendering these fields invisible in the drop down?

cheers

Like Brett Flintoff likes this

I had a similar issue when trying to use the automation rules.

My solution was to modify the workflow instead. I ended up adding a post function to the 'Issue Created' transition that set the Original Estimate field to 2h. You just have to make sure that any field updates come before the 'Creates issue Originally' step otherwise they won't be committed to the DB. See the Jira documentation here.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

Announcing Jira Service Management!

Hello there Cloud Community members! Today, we’re thrilled to announce Jira Service Management, the next generation of Jira Service Desk. Jira Service Management touts advancements in IT service ...

1,484 views 17 33
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you