How to split custom field contexts by issue type within the same project?

[nagata shumpei]

I'm trying to configure Jira custom field contexts and I'm a bit confused about how to properly split them within a single project.

What I want to achieve is:

• Use the same custom field

• Within a single project

• But have different options depending on issue types (e.g. Issue Type A and Issue Type B)

I created:

• Context 1 → Project X + Issue Type A

• Context 2 → Project X + Issue Type B

However, I'm running into issues:

• Once a project is assigned to one context, it does not appear as selectable in another context

• The default (global) context seems to block project assignment as well

• It’s not clear how to properly “release” the project from the default context

Questions:

1. Is it actually possible to use multiple contexts for the same project by splitting issue types?

2. What is the correct order of operations to split an existing global/default context into multiple contexts?

3. How should the default context be configured in this scenario?

I feel like I'm misunderstanding how Jira handles context assignment and would appreciate clarification or best practices.

Thanks in advance.

[Maria Rusnakova]

Hi @nagata shumpei

You cannot create multiple contexts for one Jira space, even if you specify a work type in the first context and want to assign the second context to a different work type.

If it's a select list and it's okay for you to create it as a cascading field, you could add the name of the work type to the parent field and options to its child.

Another option that came to my mind is to create another field with similar name or special character (f. e. '.' at the end of the name).

Best regards,

Maria

[marc -Collabello--Phase Locked-]

Hi @nagata shumpei ,

I assume this is a Jira question.  However it was tagged with Confluence cloud, so you might need to change the tags to get some attention.