Hi
I've made a couple of changes to the Bug template at the team's request. I did this via Project Settings > Issue Layout > Configure Screen
I've reordered existing fields such as 'Steps to Reproduce', 'Actual Result' and 'Expected Result' and now the data that was in these fields is no longer displaying in existing bugs. It is missing!
What can I do to locate and restore the data?
I also created a new Custom field as part of the same change but am unsure why existing fields should have been impacted by this.
Hi Stephan, from what you have shared this doesn’t make sense. Changing the layout of fields would have not impact of the underlying data. Are you sure there was data in the fields for the given issue you are viewing? If so is it possible someone deleted the data? I would run an issue query for all issues in the project with those fields displayed and analyze.
Thanks for responding. I'm confused as to what has happened as well!
I have done an advanced search for the missing data, checking that there are no variants on fields like "Actual Results" and nothing is present. The fields are empty. The only way to see what was in the fields beforehand is to view the History. I can manually copy/paste the data back in but i had hoped that there was a simple explanation and fix for this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
does the history show where the field was cleared? Any possibility of Automation stepping on the data here?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, there's nothing in the History of these issues to suggest what could have happened. There's no Automation set-up for these issue types. It's all pretty standard stuff.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To tell you the truth I’m at a loss here. I would suggest opening a support ticket with Atlassian support. If you do so, and find an answer please post back here with the findings.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.