Symptoms
If you have set up the synchronization between Jira and Spira correctly, but changes made to the requirements and/or incidents status fields are not updating in Spira (when changes to status are made in Jira), then you may have a status mapping issue or perhaps there is a timing issue between the two systems. However if the following statements are both true:
- There are no mapping errors or warnings in the event log related to the status field
- Other fields (other than status) are correctly synchronizing correctly
Then the solution is something else...
The Solution
If the previous statements are correct, then the issue is most likely to be that the product template in simply preventing bulk status changes from being made in the product:
If your product is using a template that has Status Bulk Edit = NO, then you either need to change the setting in the template to be: Status Bulk Edit = YES, or simply change the product to use a different template that does have that setting set to YES.