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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Use different default values for a custom field for the same project but different issue type



I have a custom field called 'qa/testing requirements'.

This field has been set up with a configuration scheme so that a specific default value is populated in the 'create' screen for a specific project and issue type (test sub-task).

I want a different default value to populate on the same project but a different ticket type called 'test' so that this ticket type has a different template to a 'test sub-task'


I cannot add 'test' to the same configuration scheme as it will populate the incorrect template (default value).

But if I go to add a new context (configuration scheme), the project I am looking for does not show up on the list which leads me to believe that because I have already set up a configuration scheme for that project, I cannot create another one - even though the other one would be for a different ticket type.


Can anyone tell me if that is the reason? 

And if so, are there any suggested workarounds to:

  • use Automation to add the desired template post ticket creation - which is not the ideal solution
  • use a different custom field specifically for this ticket type where I would be able to create a new configuration scheme with its own default value

And if I'm incorrect then what am I missing? 

I would have thought this was something that Jira would allow you to do. 


2 answers

1 accepted

0 votes
Answer accepted
John Funk
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 13, 2022

Hi GC,

That's because you can't have multiple contexts for the same custom field that both contain the same project. There is an open feature request that you might want to vote for and follow:

Thanks for that @John Funk much appreciated :) 

Like John Funk likes this
0 votes
Jarosław Solecki
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 02, 2023

Hi @GC , you can use the  Dynamic Forms for Jira to set different Default Values for each Issue Type in the project. 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events