Troubleshooting the 'Value for featureId is invalid' Error in API Story Updates in Jira Align
Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Given a certain data setup, JAAPI users receive an error when attempting to update a Story via API:
{'status': 'FAILED', 'status_code': 400, 'response': 'Cannot update story with id xxxxx. Value for featureId is invalid.'}
This is likely caused by the Story’s parent Feature not sharing a Program with the Story.
Environment
Jira Align
Diagnosis
This is likely caused by the Story’s parent Feature not sharing a Program with the Story.
Cause
This is likely caused by the Story’s parent Feature not sharing a Program with the Story.
Solution
1. Confirm the error is caused by different Programs
a. The Story belongs in Program 1 and is contained in Program 2 Feature
b. The parent Feature belongs to Program 2 and does not have additional programs
2. Assuming the Story and Feature do not share a Program, find out what the customer intends.
a. Was the association of parent Feature to child Story a mistake? If so, have them unlink the Story from the parent Feature. They can now update the Story via API.
i. To prevent their data from entering this state again, verify that the Approach toggle is Off for their Portfolio:
ii. If the Audit Log indicates that the connector created the association between Story and Feature, suggest a different Jira project mapping. Advisory Services recommends against multi-program approaches. If the customer has Jira Epics with Jira Stories in other Jira projects, the customer should consider mapping all of those Jira projects to the same Align program. This prevents the connector from creating multi-program Features.
b. Does the customer want to use a multi-program approach? Note that Advisory Services recommends against this as multi-program approaches cause problems for reports and data rollups.
i. If the customer wants multi-program in spite of the risks, they can enable it in Settings > Details Panels Settings: Approach
ii. They can then set a Multi-program Feature on the parent Feature and add the child Story’s Program as an Additional Program:
iii. Going forward, with Approach enabled, the connector will add the Story’s Program as an Additional Program to the parent Feature.
Was this helpful?