Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
First, you will have to create a scripted date field that calculates the difference between createdDate and resolvedDate. Or create a calculate customfield yourself.
Once that is done, you can use it in JQL as the others already mentioned here.
I have also seen reports in marketplace which does this sort of thing, but don't remember which one. Maybe you can go through the options as well.
hmm, I think with this JQL you don't get the now closed issues that took more than 50 hours to resolve. You get only the issues that are more than 50 hours unresolved.
You would need something like "resolvedDate - creationDate > 50h", but I think, this is not possible, as far as I know.
edit: took me to long to write this up. forget about this comment ^^
Isn't that all issues created in the last 50 hours, which are not resolved or closed?
From what I understood Vishnu wanted to find all issues that were resolved but took more than 50h before getting into resolved state.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs