Why can a custom field not be used when only applicable for the specific project?

This question is in reference to Atlassian Documentation: Setting up service desk reports

Why can a custom field not be used in the report filter when it's only applicable for the specific project? --> the field is greyed out in the selection and there is a hint displayed "field not applicable for project/issuetype" even if both are correct (the only service desk project in the instance and the only issuetype in this project)

Example:

Configuration:
custom field: office --> single select (office A, office B)
field context: only applicable for project "JSD1" and issuetype "problem"
project "JSD1" only uses issuetype "problem" 

Scenario:
Trying to configure a report in project "JSD1" which shows issues created for office A vs. issues created for office B.


Problem:
Field "office" can not be selected in the filter.

Note: When the field context is specified to all projects and all issuetypes (global) it works.

1 answer

This widget could not be displayed.

Because the field is only valid for one of the projects.  The other project can't report on what's not there.

but for the project in which I want to create the report, the field is valid!?

You said it wasn't.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Thursday in United States

Local Atlassian Research Workshop opportunity on Sep. 28th

We're looking for participants for another workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sh...

72 views 0 0
View post

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