Change description for Components

[Stefano Colagiacomo]

Hello I try to make this question but probably I know already the answer.

Does someone know if there is a way to change the description of Components? 

I know Components it's not a custom field but it is a System field so I can t find a way to change a description for a particular context

[Prashant Sultania]

Hello @Stefano Colagiacomo 

Your query is not clear enough either you want to change the description of the Component field or change the description of the of the components values?

However, still, I will try to answer both:

1. You cannot change the description of the component field because it is locked in both Jira Server and Jira Cloud due to the system field. However, you can still edit and add the description by using field configuration. 

2. Yes, you can change the description for each component value.

Thanks
Prashant Sultania

Note: Upvote, Like, or Accept the Answer if it resolves your query.

[Darryl Lee]

Hi @Stefano Colagiacomo!

Even though you are correct that Components is a system field, you can still change its description. Those can be customized per project/issue type (or ideally for groups of projects/issue types to make maintenance easier) using Field Configurations.

As stated on that page:

A field configuration defines the behavior of all fields available in your Jira installation, including Jira's own "built-in" fields (known as system fields) and custom fields.

For each field, a field configuration specifies:

• the description that appears under the field when an issue is edited

So if you want a different description for a certain project, you would create a field configuration specifically for that project, as detailed here:

If you want to configure the same field to have different options and default values depending on the project and issue type, check out Configuring custom field contexts. 

When defining field behavior for one or more Jira projects and issue types in these projects, you typically start by adding one or more new field configurations. You then proceed with modifying the behavior of individual fields in these new field configurations.

Finally, you can have field configurations for specific issue types, using a field configuration scheme:

You should add a new field configuration for each combination of projects and issue types, where you want to use either specific fields or fields that express particular behavior (e.g. be hidden or required).

You can then associate each new field configuration with a different issue type through a field configuration scheme. A field configuration scheme can then be associated with one or more projects. For more information, see the Overview Diagram.

Hopefully this puts you on the right track of learning about Field Configurations and how you can customize them for your needs.

Please let us know if you run into any problems or have any questions.