I am very confused about a field configuration works in Jira, especially when it comes to field contexts. I am looking at the fields available for issues and it seems fields are missing based on how the field contexts are defined.
For instance, I see "Story Points" on every issue for every project, which is exactly how the context is configured. I do not see "Change reason" for any issues, but it has the exact same context as "Story Points". Neither "Story Points" or "Change reason" are assigned to any screen.
Frankly, I do not want to see the "Change reason" field, but I do want to understand how this all works. Can someone explain this to me?
Field Contexts are very interesting.
Here's how I've used it in the past and hopefully it helps you understand.
I have a custom field (Business Name). This custom field is a Single Select Drop down.
For Project A, Business Name can have the values: A, B, C.
By adding a context, I can reuse the same field (Business Name), but give it different values.
For Project B, Business Name has values: X, Y,Z.
As you can see, same field, but different values show up based on the project that is assigned to the context.
With that said, I don't think that solves your problem with Change Reason.
I would recommend you share a screenshot of your screen configuration under the project settings. From there, for the issue type that you want to remove Change Reason, please share your actual screen (might be the same for Create,Edit,View) or share each one if they are different.
@dmimatt There are two components here. in order for a field to appear on an issue, it needs to be present on the View screen and the field context needs to be set for that issue type and/or project. If you have one and not the other, things won't work for example:
|Field on View Screen||Field Context set for issue/project||viewable|
|Field on NOT on View Screen||Field Context set for issue/project||not-viewable|
|Field on View Screen||Field Context NOT set for issue/project||not-viewable|
We use contexts extensively for every custom field created but only to limit project use. We don't usually set a context for issue types. For Server/Datacenter, this improves performance, indexing, and searching. I don't know the exact impact in cloud, but I can't image it hurts.
As an aside, you can do some really cool stuff with contexts too. For example, you cloud use a single screen scheme for all projects or a set of projects. These screens would contain a large set of fields but you could turn them on/off based on the projects. Keeps administration all in on place.
Now as far as some of the system fields (not custom) they appear on the screen layout regardless of the config it's not always obvious but is what it is.
Hi, Jira users! Do you use Jira alongside Microsoft Teams? We want to hear how you’ve used the power of Jira Cloud and Microsoft Teams (via the Jira Cloud for Microsoft Teams app) to achieve a team...
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