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

feat(issue): add statuscategorychangedate #650

Merged
merged 1 commit into from
Jan 16, 2024

Conversation

daveoy
Copy link
Contributor

@daveoy daveoy commented Dec 6, 2023

What type of PR is this?

  • feature

What this PR does / why we need it:

Open for discussion, but this field is present on REST API responses from atlassian inside my organization's tenant. It represents the time a n issue has been present in its current status and I have based some metrics on calculations from the reported time.

Special notes for your reviewer:

Understand if you don't want to merge given this field appears undocumented in the REST API. Would love to know if its present in your organization as well (atlassian may need to update their docs in this case).

Additional documentation e.g., usage docs, etc.:

api docs here: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-get

@andygrunwald
Copy link
Owner

Is anyone here from the community who can confirm the field in the response from your cloud instance is available?

@aechweeks
Copy link

@andygrunwald it is mentioned here and described in detail. You can also see that ProjectCategoryChangeEvent exists, so must it's status. I hope this helps

@andygrunwald
Copy link
Owner

@aechweeks The ProjectCategoryChangeEvent seems to be in the OnPremise version. The PR is changing the cloud version of the API here.

Thanks for the community post as well. Still no mention of cloud or on premise :(

I will wait for someone from the community to know, if someone else sees this field.

@aechweeks
Copy link

i can confirm it exists in the cloud version. is there a test i can provide you or a repo i can setup to prove it? this is def there and is the best way to check if something has or hasn't happened.

the status show here, which indicates it can be used here as an event.

for more proof:

statusCategoryChangeDate()
Similar to StatusCategory, you can issue based on the timeline using the statusCategoryChangedDate() function

Copy link
Owner

@andygrunwald andygrunwald left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@andygrunwald
Copy link
Owner

Thanks all.

@andygrunwald andygrunwald merged commit 50d59fe into andygrunwald:main Jan 16, 2024
9 of 10 checks passed
@aechweeks
Copy link

thank you! i think your burden of proof is reasonable and leads to a higher quality package.

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

Successfully merging this pull request may close these issues.

3 participants