Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Field change reports and history

Hi there!

 

There are a few questions, maybe someone has already encountered problems like this.

The following fields should be evaluable per ticket, across projects for all projects with the specific Issue type: 

Due date field for the main ticket. Sub-task due dates are not relevant. 

Original Estimate field

 

It is important to see in which project the fields have been updated. By whom and when were the fields updated.

 

Any ideas?

 

Best Regards

Jurica

 

 

1 answer

0 votes

The issue history contains a record of every change of field, recording date, time and person who did it, so you have all of that.

I think I am not understanding something though, could you explain a little more about what you are looking for?  (Beyond "it's in the history" I mean)

I'm interested in the number. If you have 20,000 tickets, in how many have been changed due date and by whom

 

I need to get a sorted list of all tickets that have changed due date and how many times it was changed

Ah, ok, I though it might be something like that.

I believe Jira to be very poor at historical reporting.  It is fine for "what are we doing now", but bad at "what happened before".

There is no simple way to get that number out of it without an app or some coding.

If you only have that single question, then I would probably take a simple approach of writing a scripted field that reads the history for changes of due date and spits out the count.  You'd then be able to run a search for "dd count > 0" and sort the results on it too.

Thanks for the information. Can I get more information here how? Thx

What approach are you thinking would work for you?  A scripted field?  Reporting tools?

I have already solved this in the way that where I first defined the date, I wrote it down with the help of an automation in Jira in one field. Then on each subsequent change the same via automation for jira said count up each change for one and records again in one field. So it's easy when you make a filter to see if the issuetyp = change counter is say 4 (there were four duedate field changes) and then in the same filter I have the first date and the last one. The ticket gets shown one field that says "Ja" and the field called duedate has changed? and all other is in Filter to see. test1.PNG

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
Community showcase
Published in Jira

Announcing the waitlist for Jira Work Management

Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...

141 views 3 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you