Tuncay Senturk _Snapbytes_ Community Champion

Sorry, now it is clear. For some reason I could not see the image you attached. I am not sure but have you tried reordering from the Jira admin > Statuses page by simply clicking up and down arrows under the Order column?

Hi @Rafal There is a ticket about this which was closed with a Won't Fix resolution. JRACLOUD-60118

Hi @Gergely Groupama Actually, the changing order of the transition buttons should do the trick. Have you clearly followed those steps?

Hi @Gergely Groupama You can change the order of the status with the workflow properties. Have a look at this article: https://confluence.atlassian.com/adminjiraserver/workflow-properties-938847526.html There is an advanced workflow configuration section, here is the link Go to To change the order of transition buttons:…

Oh ok! Thanks for sharing!

Hi @ugnė skorupskaitė Welcome to the Community! In order to edit the field, you need to add the field to the related edit screen.

Yeah, that's perfect now. For example, in your logs there is also a Blocks link to TSTPRT-7 which would also be updated, but if you add this control if (it.issueLinkType.name == "Epic-Story Link") only Epic-Story link typed issues will be updated. Thanks

Hi @Gargi Panchal The newly added post function won't affect the issues already transitioned to Done status. Whenever the transition is called, the post function which sets resolution will be called. For previous issues, you have to manually set the resolution field via bulk update option. You can run below JQL to filter…

I need the logs actually, to see the link type names for the epic.

You can use javascript to convert to any format you want. If you need further technical assistance please do not hesitate to raise a support ticket. The team will help.

If you are having issues/difficulties please raise a support ticket here and the team will help you as soon as possible.

Hi @이의석 Welcome to the Atlassian Community! Actually, the guide you already mentioned provides the solution for your needs. You can use following properties in your eazyBI reports; - slaStatus as SLA Status (whether it is MET or EXCEEDED) - startDate as SLA Start Date - endDate as SLA End Date - targetDate as SLA Target…

Thanks for sharing @Nikki Zavadska _Appfire_ 

Hi @Gargi Panchal There are two transitions to DONE status. You attached the post functions from DEPLOY to PROD status to DONE status, however, you might be using the other transition "All statuses" to DONE. Could you please check whether there is below post function in that transition as well? The Resolution of the issue…

Hi @Jean-Baptiste Bazot Welcome to the Atlassian Community! The user who resolved the ticket is not provided by Jira out of the box. You can talk to your administrator to create a custom field to store that data and fill that field with a workflow post function (as Nic proposed). However, you still won't get accurate…

Hi @Randy Knight Unfortunately, nested smart value functions are not possible at the moment. Have a look at this issue or this post.

Happy birthday @Kristján Geir Mathiesen I was born on April Fool's Day.

Oh! I'm glad that it worked. Please mark the post as answered so that it would be seen as resolved. Thanks

:D Here is the recipe

@padraik It was not meant to make it work. I just wanted to see the link-type names. Your code does not work accurately right now, it runs for every link of the issue. However, you only want to update issues of the epic. Please share the logs of the code and we will see the exact names of the link types and correct the…

Let's celebrate with Yoda Martini!

Hi @Olanrewaju Olanipekun Welcome to the Atlassian Community! As the error message says, the database you provided is not empty. If you want to upgrade your Jira, it has different instructions (link provided). However, if you want to install Jira from scratch, you have to delete all tables within the specified database.

Hi @Kavya Saritha Welcome to the Atlassian Community! Could you please provide more information? Is your Jira up and running? Have you tried different browsers? Sometimes cleaning the browser cache also helps. It might also be a network/proxy server issue. The devil is in details, we need more information.

Hi, it seems that it does not fetch the stories related to the epic. It might be because of - the link name might be wrong - the link from epic to stories might be wrong (it can be outward as well as inward) - the issue you are testing the listener code might not be an epic What I would suggest is to use the below code to…

Please check this: https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-operators/#Advancedsearchingoperatorsreference-WASWAS

Actually, it does.

Btw, I did not understand the scenario but I'm trying to help based on your code. If "Target start" custom field changes then the code will update the same custom field for the child issues of the epic.

How about this one? def change = event?.changeLog?.getRelated("ChildChangeItem")?.find{it.field == "Target start"}

Where in the code did you put that log? It should be as below def change = event?.changeLog?.getRelated("ChildChangeItem")?.find{it.field == TSField} log.warn ("change: $change")

Did you try something like this? It may shed a light. status was "Your Status" DURING (startOfDay(-30) , endOfDay() )