Changing context of custom fields

Hi All

We have about 120 custom fields and most of them have a global context.

My question is what are the advantages of limiting the scope from global to only the projects that use those custom fields?

I am aware that it will result in less re-index time.

Rahul

1 answer

1 accepted

1 vote
Accepted answer

Hi Rahul,

I give you 3 good reasons to use specific context (for project):

1) in the simple research mode, on the left panel, you find actually global customfields (CF) : if you have 120 CF, you have a list of 120 CF : Not very fun for users. When you define a specific context (for a project), you can see CF depending on the projects you only select

2) In the DB, using global CF, a value (even Null) is allocated for every single issue you create (I did the control myself using a jira 4.4.4 plateform). It means when you create 1 issue, you reserve 120 space, often pointlessly. Take care if you have a lot of issues (I've got +300K)

3) It will be more easier to customise specific values, for projects, using the same customfield, in the future!

I've got 140 CF, only 7 are global.

I hope you understand, sorry for my level in english, I need to practice!

Thanks Stephane...

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,725 views 17 21
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you