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

Tempo Team field interferes with Portfolio team field preventing inheritance of team field

My company has Tempo on our Jira account and ever since, we cannot use the workflow to set up post functions that inherit the Portfolio "Team" field from the parent task. The workflow only gives the option for one team field, which doesn't make sense because the Tempo "Team" field and the Portfolio "Team" field have different ids. I cannot use automation for Jira to achieve this either because the Portfolio "Team" field isn't an available option.

This is very frustrating because our team field is what our boards are filtering by for our teams. Is there a workaround for this? I have searched far and wide on these forums but to no avail. 

1 answer

1 accepted

1 vote
Answer accepted

Hi @Geoffrey Melle,

I don't think this has anything to do with Tempo being in your instance alongside advanced roadmaps. But setting the field is indeed not supported through plain selection.

I have struggled with setting the Team field when I wanted to set a default value to it. And a fellow Community leader helped me out greatly in this thread.

To retake the headline:

Rule

Go to Automation, and choose to create a new rule. Set the components as follows:

  • Trigger: Issue Created
  • Action: Edit Issue

In Edit Issue, select "More Options" then in the Additional Fields section enter:

{
"fields": {
"customfield_10123":"5"

    }
}

^ In this example, 10123 is the Team field's custom field ID, and 5 is the Team ID

Obviously, your trigger may be something else as well.  

Thanks Walter, this did work for me. Actually a colleague of mine sent this fix to me this morning. I am still annoyed that we cannot use this team field in a post function within the workflow. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,047 views 8 28
Join discussion

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