Petter Gonçalves Atlassian Team

Hello Javier, Thank you for raising this question. JIRA Core does not have a functionality to automatically transition sub-task issues when its parent is transitioned, however, there are some add-ons that give you this feature. I recommend you to try Automation lite for JIRA and configure automation rules like the example…

Hello Lance, As you can see in this documentation, The JQL function issuesInEpics that you are trying to use is not available on the cloud version of ScriptRunner yet, so this option will not work for you on Cloud. That been said, there are other add-ons that provide you a similar functionality on JIRA Cloud. I recommend…

Hello Clayton, Unfortunately, it is now possible to return issues that have spent a specific amount of days in status, however, there are some add-ons that can provide you with this information. That been said, you can use the Pivot by Statuses report provided by the Time Reports add-on to get this information: Let us know…

Hello Dan, Welcome to Atlassian Community! Unfortunately, JIRA does not measure the time logged for sub-tasks in agile reports, only User Stories are taking into account. This is a good practice based on Agile methodology, however, the pain point is that the Sub-task estimation is not automatically added to the parent…

Hello Laas, Thank you for sharing the behavior you are facing. After digging a little bit further on this, I think you are being impacted by the following bug: - Suite Utilities for JIRA - Time spent in source status in transition tab behaves erratically at times Feel free to watch the bug to receive notifications about…

Hello Simon, Currently, it is not possible to directly compare two custom field values using only a JQL query, but we have a feature request to implement it for Version custom fields: - Add ability to compare version fields using JQL Feel free to vote and watch the suggestion to increase its priority and also receive…

Hello Simon, Thank for sharing your problem with us. Digging a little further on this, I was able to find and reproduce the following bug that should be causing your issues: Default post functions order causing values added in transition to be denied with certain status' property Unfortunately, I was not able to find any…

Hello Harshraj, The Story option that appears in the drop-down when you are creating an issue is an Issue type. It defines which kind of issue you are creating. You can create multiple issues with the Story issue type, you just need to select it in the issue creation page when you click to create a new issue. There are…

Hello Mandy, welcome to Atlassian community! Can you please confirm if you are using JIRA Cloud? If you are, can you confirm if you are using a Classic project or a next-gen project? If it is a next-gen, the following message will appear in the bottom of the left menu: As you may not know, Next-gen and classic projects use…

Hello Polina, Welcome to Atlassian community! Just a suggestion: There is a free plugin that sums the time estimation of related issues in the Epic without needing any code: - Epic Sum Up - Light Using Scrptrunner, you can use the script documented in the link below, except use "Epic-Story Link" instead of the example…

Hello Johannes, Just to make sure, when you say "object type" you are meaning an issue type of JIRA, is that correct? If that's the case, you can achieve your goal by performing the steps below: - Create a new Custom issue type Equipment and add it to the relevant projects - Create a User picker custom field to get…

Hello Jonathan, After some time investigating, I was able to reproduce your issue and properly understand it. Please, check the answer below for more details about its root cause and how to work around it: Story point/Story point estimate fields

Hello Shweta, Welcome to Atlassian Community. Today, your project templates are split into two types on JIRA Cloud: Classic and Next-gen projects. As you may know, both projects use their own issue types and have different time tracking methods, which uses two different fields: - On Classic projects, the estimation is…

Hello Pooja, I understand that you would like to set the ticket reporter with the e-mail address of the person who created the ticket through e-mail on JIRA Service Desk, is that correct? If that's what you are trying to do, I would like to let you know that this happens by default on JIRA Service Desk when you configure…

You are welcome, Marcela. Let us know if you face any questions regarding it.

Hello Jordan, Can you please confirm if you are using JIRA Cloud or Server? There are several ways you can configure your Kanban project to manage your issues, it will just depend on what kind of data are relevant for your reports. Based on the information you have provided so far, I would proceed with the following: - I…

Hello Tawhid, The Affect version/s field is related to the current versions that you have configured for your project. Can you confirm if you are using JIRA Server or Cloud? If you are on Cloud, can you confirm if you are using a classic or a next-gen project? I would check the following steps on a classic project: 1 -…

Hello Anuj, Welcome to Atlassian community. You can extend your JRJC Script it with a method that wraps JIRA REST API Call: - Set the 'Epic Link' via REST call Or you can use implementation from Atlassian: https://marketplace.atlassian.com/plugins/com.atlassian.jira.jira-rest-java-client The code snippet for REST Java…

Hello Yongguang, Can you please confirm if the issue still happening? As @Nic Brough -Adaptavist- mentioned, there are no problems on JIRA Cloud that could be causing it, so I believe you were facing a cache problem with your browser. If the problem keeps happening, try to clear your browser cache and restart it. If it…

Thank you very much for this useful data, Andreas! We will provide this info to our developers so they can properly troubleshoot and fix this lack.

You are welcome, Adriana! Have a nice week.

Hello Steve, Yes, the Sum-up add-on works on JIRA Cloud too and have the exact gadget you are looking for: the sumUp Two dimensional Filter Gadget Please, give it a try and let me know if this is what you are looking for.

Hello Boris, The pop-up window that you see when you try to move your issue in your board is a default message and happens for anything that would block you to perform such transition, not necessarily the Condition. In fact, the pop-up message is not related to the condition, but to the fact that you are not able to…

Hello Steve, Could you please provide us a screenshot of the current widget you have configured so we can have a better idea of your goal? I understood that you are looking for a way to sum up the story points of all issues assigned to a specific user and display it on a gadget. Is it correct? If I have properly understood…

Hello Andreas, Indeed, it seems we have a new bug that is causing this odd behavior on JIRA boards. Here is the official report: - Backlog tab missing due to having 2 Kanban backlog column Since this is a new bug, we are still investigating what could be probably causing it. Can you please let us know what columns you…

Olá Catarina, Acredito que você possa estar tendo um erro no index da sua aplicação ou um conflito com o outro issue type com o mesmo nome. Poderia me dizer se quando você filtra pelo outro test issue type o filtro apresenta algum resultado? Sugiro que você faça um background re-index de sua instancia seguindo as…

Olá Catarina, As colunas selecionadas para os filtros do JIRA aplicam em um contexto global, ou seja, irão mostrar exatamente as mesma informação para todos os filtros. Dito isto, a única forma existente de ver colunas customizadas para cada filtro seria configurando múltiplos gadgets do tipo resultado de filtro para…

Hello Dean, Unfortunately, I'm afraid this option is not available on JIRA, however, we have created a feature request to add the functionality to select epics when creating issues through e-mail: - Create issue via email directly in a specific Epic Feel free to vote and watch the suggestion to increase its priority and…

You are welcome, Christopher! Have a nice weekend and let us know if you find any new questions about it.

Hello Marcela, I think the best way to record historical data in a displayable way for a gadget would be by adding sub-tasks to an issue. You could even add a field to categorize the data by date, type or any other parameters. The steps would be: - Create a task and name it as you want. E.G: Historical data - Add one…