Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to make a Change Log table for a Jira Cloud Project?

Hello everyone,

I would like to know which would be the more efficient way to make a change log for each project that we are managing... We already use the activity streams for each ticket, but we need to be able to see and analyze these changes in a table, this way we can filter what itens we are interested and would not need to go from one ticket to another gathering/looking for this info.

Does someone had already worked on something like this? Or have any insights on better ways to solve this?


Thanks :) !

2 answers

0 votes
yuliia_b__SaaSJet_ Marketplace Partner Aug 31, 2022

Hi @tiagoPiresENG 

It's possible to create a change log table for the list of issues. The case you've described is the reason why our team developed Issue History for Jira. The app helps to create the report you need. Just add any standard or custom field to the grid's columns.

Here is an example of how it looks:

assignee activity in jira.png

There is 30-days free trial, so you can check if it can help you.

0 votes
Pramodh M Community Leader Aug 31, 2022

Hi @tiagoPiresENG 

Welcome to the Community!!

I would not recommend doing that, since if an Organization has to grow they have to look at the big picture and not what's happening at the issue level right?

Being said that, each issue has its own history section to track the changes that happened over time for audits or any records. JQL is there for you to search/filter the issues.

Is there any specific requirement you are trying to achieve by having to look at the changelog of the tickets?

Let me know


What our team needs is just to have a table with each row being a update made on a ticket. The columns on the table would be useful information for our audit, such as who made the update, what changed on this update, when it happened, which products are affected by this ticket, the priority and of course in what ticket has this change happened. We had a table somewhat like that before migrating to the cloud and now we are willing to make it again, but we will need a new method.

That being said how do you think we could use JQL on this matter? We haven't tried using it yet I think.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events