-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
8.20.0, 9.3.0, 10.3.0, 10.4.0
-
8.2
-
7
-
Severity 3 - Minor
-
0
-
Summary
Even when the date picker custom field context is configured for projects and issue types that are retrieved by the Plan's issue source, the date picker custom field is still greyed out and cannot be selected.
According to our documentation, for the field to be available it needs to be:
- In the scope of all projects in a plan (technically - all projects from all issue sources (including filters) in a plan)
- In the scope of all issue types in a plan
- Be the custom field type of date picker (in the DB it's "com.atlassian.jira.plugin.system.customfieldtypes:datepicker")
Steps to reproduce
- Create a project, with a few issue types (let's say; bug, epic, story).
- Create a date picker custom field.
- Set context to the above project for the bug, epic, story issue types.
- Go to plan > configure > scheduling
Expected result
The date picker custom field can be selected for the plan's scheduling.
Actual result
The date picker custom field appears greyed out and cannot be selected for the plan's scheduling.
Workaround
- Set the custom field context to global context
- Set the custom field to the project retrieved by the Plan's issue source, but for all issue types
- is duplicated by
-
JSWSERVER-21790 The field context configuration prevent Advanced Roadmaps to use it as start/end dates fields
-
- Gathering Impact
-
- is related to
-
JSWSERVER-25096 Allow Custom field date with its context to certain issue types to be selected as an End Date
- Gathering Interest
- links to
- mentioned in
-
Page Loading...