Fabian Lim Community Champion

Thanks for sharing @Jennifer Flinn We started using this plugin a few months ago in DC and we would benefit from having this functionality.

From the screenshot, it looks like you have to use the "is a parent of" relationship instead of "is a child of". Try it and let us know.

Hi @Donna Macauley This is not possible right now. There is an open ticket with attlassian: https://jira.atlassian.com/browse/CONFCLOUD-70954?error=login_required&error_description=Login+required&state=54dd7c34-09a2-40e4-952f-10b890108136 You will have to look at the marketplace for apps that have this functionality.

For those who are interested, here is a video turorial that explains it: https://youtu.be/DcPYrw-Puus Just need to follow Mikael's branch changes.

Here is a video tutorial on how to do it as well via jira automation: https://youtu.be/DcPYrw-Puus

Check this out. This an old post where I pasted an image or our dashboard: https://community.atlassian.com/t5/Jira-Service-Management/What-do-you-report-on-in-your-service-dashboard-share-pictures/qaq-p/1703537

For the runnerlog: https://confluence.cprime.io/plugins/servlet/mobile?contentId=6558203#content/view/6558203 It would be runnerLog("new issue:" + newKey);

Hi @Nerses Here are some videos for Tempo Timesheets: https://www.youtube.com/watch?v=r971lFbwVTE You can contact me in LinkedIn and we could discuss a solution for you. Regards, Fabian

Hi @Dinael Silva Yes you can use the created field and mix it with different options outlined in this link: https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-fields/ If you are using eazybi, this is also possible without a jql.

@Dinael Silva Good choices. We use eazybi and mix it with confluence to add context to the graphs. The description features are limited and we don't want users to change the reports by mistake. Cheers,

Hi @Konstantin Balashow Click on the legend of the measure and change the type. Link: https://docs.eazybi.com/eazybi/analyze-and-visualize/create-charts Cheers

Hi @kateryna_lytvynchuk Take a look at this tutorial: https://youtu.be/DcPYrw-Puus It's the first rule that you want to look at. Regards

It's actually the create function that is causing the issue. Why don't you share the whole script?

Hi @Midnite8 Try printing the new key with a runnerlog and you will see if it's creating the issue or not. You are correct with your assessment, so something happened with the create function, maybe one of the fields are missing or have not been configured. Thanks

Hola Juan, No creo se pueda con el JQL. Vas a tener que buscar el el market place si existe un plugin. Saludos, Fabian 

Hola @Eric Díaz Bizama Saludos desde Canadá. Las categorías para los estados no se pueden cambiar. Sola hay tres: To Do, In Progress and Done. Por ejemplo el estado "COMPLETED" en las mayorias de veces es de la categoria "Done". La otra opcion es tener otro campo (customfield) que define las catogorias de las incidencias.…

Thanks for sharing @Daniel Ebers We will have to install this in our DC environment.

Hola Dante, Para poder ver algo en este reporte, tienes que tener tickets que hayan sido resueltos. Aunque el status puede estar en "DONE/COMPLETED", tienes que tener el field "resolution" con algo que on sea "unresolved". Ejemplo debajo: Es posible que en tu proyecto no estes añadiendo el field "Resolution". Saludos.

Hi @Magdalena Migas You can use the issue field changed jira automation. Take a look at this video link: https://youtu.be/DcPYrw-Puus Look at the second rule, but you will have to reverse the brach to occur in the parent issue type instead. Thanks

Hi there, Jira automation also provides this functionality. Here is a video tutorial link: https://youtu.be/DcPYrw-Puus Regards.

You could also use the jira automation plugin. * Here is a video tutorial. Take a look at the second rule. Instead of editing fields you can transition all subtasks to a new status: https://youtu.be/DcPYrw-Puus Regards 

Most likely you are using the other automation. In that case follow this: Trigger: issue created Condition: specify that the project is the jsm project Action: clone issue, where you select what you want to copy and the destination project. Action: link issue to the newly created issue. Note: this rule must be created…

Bringing stories that are in another sprint board the qa sprint can csuse issues when you assign them to another sprint board. I will go with my reco 4 and have a dashboard that shows all tickets in qa status status so you can plan the qa work. 

Hi @Jenn Molyneaux, Does the QA manager want to have a sprint board within the blue project or a central one that picks up various projects? 

@Anthony Mazzei As far as i know this is not possible. You will have to create a custom field that will hold the release values. Either using a select field and populating all the options manually. Them make it available to all the projects that need it in their screens. For one of our clients we used insight asset…

It depends on you. You could use it when the issue is transitioned, field changes values, issue is updated. I would use field changes values since they could change very often. However, you have to ensure that both fields are always populated. This is an example: https://youtu.be/60sWD66l19k Your rule will be: Trigger:…

Hi @Jyothi Ravipati Take a look at the smart values date functions: https://support.atlassian.com/jira-software-cloud/docs/smart-values-date-and-time-functions/ {{[date1].diff([date2]).[unit]}}<br> Returns the amount of time between date1 and date2, in the unit specified. If date2 is earlier than date1, the value returned…

Hi @ericamlie Yes you can use the balanced workload. Here is a video with details: https://youtu.be/hEh3MsoUxho

@jfgmail This video explains the functionality in detail with the other options too: https://youtu.be/hEh3MsoUxho Thanks

@Jamshaid One option you may consider is to write on a custom field the time the ticket was transitioned with jira automation. That way you can export it as a field.