You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I would like to know if there is a way to get information from Jira tickets and append it to a on-going list?
I looked through some of the documentation but im not sure what i would need or if there is an application i can use.
The only options i found so far is to either export the ticket as a XML or Word.
Hi @Tory Dennis -- Welcome to the Atlassian Community!
What problem are you trying to solve by doing this? How would the team(s) behave differently if you had that information right now?
Knowing these things may help provide some context so the community can offer suggestions. Thanks!
Kind regards,
Bill
@Bill Sheboytrying to get a list of all my latest software release in one place instead of having to go back through previous tickets and or emails to determine if that package release would have affected multiple servers.
For an example if i had 30 packages released and for someone reason there is an issue that is affecting multiple servers, i would have to go back through all of my releases to determine which package would have affected those servers. So instead of looking through emails and notifications sent my jira i would have a file that contains every package name or ticket number from jira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, Tory.
Is there a JQL statement you can write that can return what you need?
If not, you could investigate either creating an automation rule, or using a webhook on specific changes, and build another application which adds to your information store.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.