Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exporting state_reason attribute in .csv file #119

Open
chiragvidani opened this issue May 24, 2024 · 4 comments · May be fixed by #120
Open

Exporting state_reason attribute in .csv file #119

chiragvidani opened this issue May 24, 2024 · 4 comments · May be fixed by #120

Comments

@chiragvidani
Copy link

Enhancement Title

Exporting state_reason attribute in .csv file

Problem statement

GitHub closed issue status are of 2 types:

  1. Closed as completed: For done, closed, fixed, resolved.
  2. 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
@austinStan
Copy link

Hi @chiragvidani ..im a newbie..is this still available?

@chiragvidani
Copy link
Author

Hi @chiragvidani ..im a newbie..is this still available?

@austinStan couldn't get you. please elaborte.

@austinStan
Copy link

@chiragvidani i wanted to contribute but im still a beginner.I was wondering if the issue was open

@chiragvidani
Copy link
Author

@chiragvidani i wanted to contribute but im still a beginner.I was wondering if the issue was open

I have raised the PR #120 for this issue, waiting for the contributors to review and merge it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants