Hey everyone,
I’m working on a project that needs to grab the activity info for Jira issues. Does anyone know if there’s an API or some other way to get this data?
Here’s the deal: my app makes issue payloads and sends them to Cosmos when a webhook goes off. But we’ve hit a snag with Xray issue types (like test, test plan, and test set). When these are brought in through the Test Case Importer, the issue’s updated timestamp stays the same and no events fire off.
If I could get my hands on the activity data, it might help solve this problem. Any ideas on how to tackle this? Maybe there’s a better way to handle it that I’m not seeing?
Thanks for any help you can give!
Yo MarkSeeker91, have u tried using the Jira REST API? It’s got an endpoint for issue history (/rest/api/2/issue/{issueIdOrKey}/changelog). might help u grab that activity data ur after. just remember to set up proper auth n stuff. good luck mate!
I’ve dealt with similar issues in Jira Data Center, and I can suggest a couple of approaches. First, have you looked into using the Jira Software Cloud REST API? It offers more granular access to issue data, including activity logs. You might find it more comprehensive than the standard Jira REST API.
Another option is to utilize Jira’s Audit Log. It captures a wide range of activities, including those that might not trigger webhooks. You can access this through the API or export it directly from Jira’s interface.
For Xray-specific issues, consider implementing a custom listener. This can capture events that standard webhooks might miss, especially for imported test cases.
Lastly, if you have the necessary permissions, querying Jira’s database directly could provide the most detailed activity data. Just be cautious with this approach to avoid performance impacts.
Hey there, MarkSeeker91. I’ve been in a similar situation before, and I can tell you it’s a bit tricky. The Jira REST API is definitely a good starting point, but it might not give you the full picture for those Xray issue types.
In my experience, I found that using a combination of the REST API and Jira’s database was the most effective approach. If you have access to the database (which you should in Data Center), you can query the tables directly for more detailed activity data.
One thing to keep in mind: this method requires some SQL knowledge and careful handling to avoid impacting Jira’s performance. It’s not the most straightforward solution, but it worked wonders for my team when we needed to track those elusive updates.
Have you considered reaching out to the Xray team? They might have some insights on how their importer interacts with Jira’s activity tracking. It could save you a lot of headaches down the line.