Details
-
Bug
-
Resolution: Timed out
-
Low
-
None
-
4.4.5, 5.0.3
-
4.04
-
1
-
Severity 3 - Minor
-
-
Description
When creating a custom field of any issue type and with Global Context, it will apply to all issues in JIRA.
And, when creating a 'context A' for a custom field of issue type 'Task' and project 'BLUE', for example, the other Issue Types on the project 'BLUE' should use the 'Default configuration' of the custom field created first since it's global. However, this doesn't happen. Every other Issue Type on the project 'BLUE' "loses" the custom field.
Steps to reproduce:
- Create a project named BLUE and a project named RED
- Create a Select List custom field for any issue type and with Global Context
- Set list options: Hello, Goodbye
- Create a "Context A" for the Issue Type TASK and for the project BLUE
- Set list options: Easy, Difficult
Expected behavior:
- When creating an issue with Issue Type BUG in the project RED it should display 'Hello' and 'Goodbye' options in the custom field
- When creating an issue with Issue Type TASK in the project BLUE it should display 'Easy' and 'Difficult' options in the custom field
- When creating an issue with Issue Type IMPROVEMENT (or any other but TASK) in the project BLUE it should display 'Hello' and 'Goodbye' options in the custom field
What happens:
- When creating an issue with Issue Type BUG in the project RED it will display 'Hello' and 'Goodbye' options in the custom field
- When creating an issue with Issue Type TASK in the project BLUE it will display 'Easy' and 'Difficult' options in the custom field
- When creating an issue with Issue Type IMPROVEMENT (or any other but TASK) in the project BLUE it will not display any custom field