You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Closed as completed: For done, closed, fixed, resolved.
Closed as not planned: For won't fix, can't repro, duplicate, stale
So, when trying to filter on the closed state in .csv export, it doesn't give information on whether the issue is completed or not planned.
Solution
This data is available with an attribute state_reason, adding it as the default attribute in the .csv exported file.
I can understand that this can be exported using a specific attribute option, but on using the exportAttributes option, we need to specify all the required attributes as default ones are skipped.
So, I think the ideal solution is to include state_reason in default attributes, as this value gives more information on the type of closed state
The text was updated successfully, but these errors were encountered:
Enhancement Title
Exporting
state_reason
attribute in .csv fileProblem statement
GitHub
closed
issue status are of 2 types:So, when trying to filter on the
closed
state in .csv export, it doesn't give information on whether the issue is completed or not planned.Solution
state_reason
, adding it as the default attribute in the.csv
exported file.exportAttributes
option, we need to specify all the required attributes as default ones are skipped.state_reason
in default attributes, as this value gives more information on the type ofclosed
stateThe text was updated successfully, but these errors were encountered: