Impossible to save Work item because of conflict
Hello,
Our team in encountering a problem with specific work items.
We have a work item 372 that is linked with a second work item 3780 from another project area.
When we try to save modifications on those two work items we have the following error:
After a refresh of both Work items it is still not possible to save the modification. There's nothing in the server log related to that problem.
We are using RTC v4.0.5.
Thanks in advance for your help!
|
Accepted answer
Hi. Tim
There are some reports on the similar issue you are encountering and the possible causes are: 1)Server cache 2) ETL jobs running or failure For 1), you need to restart the server For 2) Waiting for ETL to complete and fixing any ETL problems required(if ETL job has any issues, you can check with ccm-etl.job to see if there is any clues). Thanks Tim De Becker selected this answer as the correct answer
|
4 other answers
Hi,
Thank you for your help, restarting the server resolved the problem.
I hope we will not have this issue too often...
Thanks,
|
We are having this problem and a server restart did not resolve the issue. Our ETL jobs appear to be running without incident. Are there any other options besides filing a support request with IBM?
Comments
Nate Decker
commented Jan 05 '17, 11:58 a.m.
In our environment, one of our custom follow-up actions causes this to happen in certain circumstances. To test whether that is a factor, try using a role where no pre-conditions or followup actions are enabled. |
I don't know of any other solution.
|
A defect was opened for this issue. See more details below:
https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=369390 |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
we saw this a few times on 4.0.4 too.. only a server restart resolved the problem.
in our case, the workitem was a few weeks old, and was last updated the day before the problem occurred.
I no longer work there, so don't know if they resolved the problem thru support.