-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Medium
-
None
-
Affects Version/s: 11.8.1
-
Component/s: Epics - Attribute
-
1
-
Severity 3 - Minor
-
No
Issue Summary
Currently, in Jira Align, when a custom field designated for an Epic (as set in the Details Panel Settings) is turned off or deleted, the data for that custom field remains stored in the Jira Align database. This situation impacts the API by preventing users from successfully executing PATCH requests for affected Epics.
When users attempt to run a PATCH request on these Epics, the Jira Align API returns an error related to the values in the custom field. Consequently, users must access the Jira Align UI and manually save the affected Epics to clear those fields.
The custom field can be located in various tabs of the Epics, such as the General and Intake tabs.
Steps to Reproduce
- Create custom fields for Epics in the Details Panel Settings
- Can be in the Intake tab
- On Epics save values for the custom fields
- Go back to the Details Panel Settings and delete the custom fields
- Now, using the Jira Align API, try to PATCH the Epic used
Expected Results
The PATCH worked well and the Epic is updated
Actual Results
The Jira Align API returns an error when trying to PATCH:
Option ID is invalid
Workaround
The workaround for this is going to the Jira Align UI and click on save in the Epic.
- is connected to
-
JAROT-530 Loading...