Composer deletes and replaces artifact
A couple of users have ran into a problem. Here the email I recieved:
They were present this morning. I opened and removed green highlighting and went to save. It responded that it couldn't be saved and then created the file "rrc421" and now my document is no longer present. The file rrc421 is corrupt and has a java error dump. The other users had luck recreating this error - this is what they said: deleted when changes are made to an artifact in Composer. However, it doesn't happen all of the time so I'm not sure what the root cause is. Here's what I did: 1. Copied one line of text associated with a bullet point in one requirements artifact and pasted into a bulleted list in another artifact. The line was pasted over an existing bulleted list item. 2. Select the new bullet item and add a fill color to highlight the text. Save the artifact and close the artifact. 3. Re-open the artifact, select the highlighted bullet item and change the fill back to 'Automatic'. Save and close the artifact. 4. Re-open the artifact and the text for the bullet item is missing. There isn't any consistency around when this will happen or why. I've noticed it when I've been working in Composer for a while during the day but I was able to reproduce the problem first thing this morning We are running composer 1.0.0.1. |
2 answers
When the name of the artifact changes to rrc# like that, it's probably a good indication that the stored content of the artifact has become corrupted (and thus the indexed name is "lost"). It is still the same file, the rrc# is the permalink name. So the bottom line of this is we'd need to investigate why those steps are potentially corrupting your artifact.
In the meantime there are a couple of things you might check. First, are you able to download that artifact? If so, it would give us a peek into the raw content of the artifact and possibly make it apparent why/how it's become corrupt. Does the artifact open in an editor at all? If so, then you would be able to access the history and potentially restore a previous, valid revision. Finally, if you could provide the .log file from the client, it will give us additional clues about what's happened to the artifact. |
Getting us the .log file will be helpful. This sounds, in part, like another defect that we identified and fixed as a hotfix on top of 1.0.0.1. In that case, you would end up corrupting the document if you tried to set the font or background color of an anchor (hyperlink).
|
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.