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

Richard Bergmann July 6, 2016

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.

2 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 6, 2016

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

Richard Bergmann July 6, 2016

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

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 6, 2016

You said it wasn't.

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 6, 2019

Closed because this is attracting necroposting spam.

TAGS
AUG Leaders

Atlassian Community Events