Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Associate a Project to multiple Field Configuration Schemes

In our instance we have a mandatory requirement on 'Log Work' field to be entered for all issue types. I would like to remove this required field from issue type 'Epic'

I have created new Field Configurations and Field Configuration Schemes and associated issue type 'epic' to it.

How do I associate Project X to FCS while still allowing Project X to be apart of its existing FCS?

Also open to other suggestions.

Thanks in advance/

2 answers

0 votes

Hi Antonio,

If I understand your use case correctly, you need two different field configurations that you could assign to different issue types (one for 'Epics' without the 'Log Work' and one for all other issue types with 'Log Work') . Would that work?

Hey @Carlos Garcia Navarro ,

Your understanding is correct.

In Jira Settigs-> Issues-> Field Configuration Schemes, you can edit your field configuration scheme and assign different field configurations to different issue types. Maybe you can have one for epics and another one for the rest. Would that work?

Screen Shot 2021-04-10 at 11.32.47 PM.png

Hey @Carlos Garcia Navarro

I already followed those steps in the screenshot but my issue is this new FCS is not associated with a project so nothing has changed for epics.

If I make changes to the project, it will affect the other issue types which I don't want to do, just isolate epics. 

0 votes
stivas I'm New Here Apr 10, 2021

In our case we have an obligatory prerequisite on 'Log Work' field to be entered for all issue types. I might want to eliminate this necessary field from issue type 'Epic'

I have made new Field Configurations and Field Configuration Schemes and related issue type 'epic' to it. 

@stivas 

But it still needs to be linked to a project in order to work from my understanding which is where I am stuck.

Suggest an answer

Log in or Sign up to answer
TAGS

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