I created and used a filter. I chose a number of fields to show on screen for each ticket part of the filter result. This result is OK. But when I export the filter result showed on screen using the "Export in another format" option, selecting "for the fields showed in screen", the exported results, in a .csv file, don't match the screen results: some fields are gone and new ones appear.
How can I resolve this situation: I need the missed fields et don't care about the new ones.
Thanks
Personalized field and description field are missing. I select the "fix_version" field but this one is duplicated 3 times in my exported files (fix_version1, fix_version2 and fix_version3). The "sprint" is added in my exported file results and duplicated 4 times (sprint_1, sprint_2, sprint_3 and sprint_4). No calculated field.
can you provide more info? what fields are missing and what extra fields are presented. I know that there will be some additional fields, e.g. a unique issue ID, created date, etc. and some fields are not actually fields but rather calculated results.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
let's keep the discussion w/in the thread using the "Reply" rather than "Answer".
I tried the Description and was surprised to see it was not exported as well. I can't recall if it used to be or not. The reason you have multiple fix version fields (and sprint fields) is that if you have more than one fix version listed in one or more of the issues. each version (sprint) will result in a unique entry.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But it doesn't explain why my chosen fields aren't exported and new unchosen fields are added to my exported file results. Like I said, I didn't choose the sprint field and this one was added in my exported file results.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I cannot explain that. it is not happening to me. You might wish to raise an issue w/ Atlassian Support to see if they can analyze/answer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.