Trudy P Claspill Community Champion

A quick check of Actions and Conditions available in Automation indicates there is no Automation function to check if an email matches a Jira user. Have you investigated the Jira REST API?

Hello @Boris Libeert Welcome to the Atlassian community. In looking at my own Free instance of Jira the "new" functionality you describe occurs for me only when I am using the Epic panel in the Backlog screen for a Team Managed project. The "old" functionality you describe happens for me when I am using the Epic panel in…

Hello @Jamie Edmondson Welcome to the Atlassian community. According to the vendor documentation there are limitations on that feature. Schedule one issue for multiple Resources Jira by default doesn’t allow assigning one ticket to multiple assignee, with ProScheduler that’s possible. This feature has limitation and only…

Yes, ideally we do want to take an action using automation upon certain status changes. There are multiple ways to address this need in both Jira Cloud and Jira Data Center: - modify the Workflow Transitions of interest to include Post Functions to execute the necessary actions - use the Automation for Jira feature which…

Hello @Lauren Hinrichs What exactly do you mean by "understand"? Do you need a report that lists the date and time of each status change for every issue? Do you need to take an action automatically when a status change occurs? Please provide more details about the problem you are trying to solve.

Hello @Orly Dahan First addressing If the email does not have a Jira account. an error message pops up in the automation. You can't have a pop-up error message for an Automation rule. Automation rules by their nature are not interactive (excluding manually triggered rules which also allow for prompting for input). You…

Hello @Stephen Doggette The portion of the board configuration you are highlighting impacts the fields that will display in the issue view that opens to the right of the board. This display opens if you have selected "Open issues in sidebar" from the board options. The only relationship between the Issue Detail View in…

Hello @Tuğçe Duranay If you are using a paid plan for Jira then I advise you to contact Atlassian support directly, if the issue keeps happening. A Jira Admin, Site Admin, or Organization Admin will be able to open an Atlassian support case at: https://support.atlassian.com/contact/#/

Hello @idepardazan dornian Welcome to the Atlassian community. You need to have the Time Tracking field added to the issue type(s) in your project. Do you have that field assigned to the issue types? If you do then click on the ... button in the upper right corner of the issue details display and you should find a Log Work…

Hello @Sohail Alam You can augment condition where you are checking for Subtasks to ensure there are none with "TEST" (or whatever key word appears in your subtask summary) are present.

This appears to be a duplicate of your other post here: https://community.atlassian.com/t5/Jira-Service-Management/How-to-creating-Sub-tasks-one-time-only/qaq-p/2449519

Hello @Leo Cheung Welcome to the Atlassian community. That screen is showing you how many of the Free licenses have been used. You have granted 5 people access to Jira Software, so you have 5 more free licenses available for Jira Software. You have not granted any users access to Jira Work Management, so you it is showing…

Hello @[deleted] Welcome to the Atlassian community. Have you tried a different browser? Are there other users that use the same browser as you that are/aren't experiencing the problem?

Hello @Joshua Packwood Welcome to the Atlassian community. Are you referring to the Timeline view for a Jira Work Management project? I am guessing you are because you mentioned the List view which applies only to JWM projects. If you are in a JWM project be advised that the Timeline view does not support the Group…

Hi @Jim Smith Sorry, I've been multi-tasking and not giving you complete answers. I'm focused now. :-) In this step replace {{#changelog.epic link}}{{toString}}{{/}} with {{issue.epic link}} If you tried to use {{issue.key}} here it would be looking at the key of the trigger issue, not the Epic Link field of the trigger…

I see that you started a separate Question, so I will discontinue responses here. https://community.atlassian.com/t5/Jira-Software-questions/Summing-up-the-story-points-from-task-that-are-link-to-a-story/qaq-p/2448864

You don't need this smart value at all anywhere: {{#changelog.epic link}}{{toString}}{{/}} This rule is running against that has already been confirmed to be linked to an Epic. You don't need to reference the changelog at all. In the Lookup Issues action replace {{#changelog.epic link}}{{toString}}{{/}} with {{issue.key}}…

Hola, Los tableros están limitados a mostrar hasta 5000 problemas. Si tiene más de 5000 subtareas, no puede mostrarlas todas en un tablero. Esto también se aplica a la visualización de Backlog. Tendrá que crear filtros que seleccionen menos de 5000 problemas a la vez y usar varios tableros para ver la información. ---…

Can you show us the changed rule? If you have changed the For branch to use "Epic (parent)" then in the Lookup Issues action use "{{issue.key}}" instead of "{{#changelog... {{/}}"

You can find Screen information under Project Settings > Issues > Screens. Also check for the field under Project Settings > Issues > Layout.

@Sandeep Kumar Vikrant provided the correct answer.

Good find, @Vikrant Yadav ! I had not noticed this limitation with the Free version.

Hello @Marja Kalinke Do you the "relates to" link type in Tasks ONLY to relate them to their "parent" Story? Or do you use "relates to" in Tasks to link the Tasks to other types of issues for other reasons?

Hello @조형현/(협력사) 책임/D2C서비스기획파트 Welcome to the Atlassian community. Are you accessing Jira through an email account that you set up yourself, or through one set up by your employer (or a previous employer)? If you are using an email account set up my a current or previous employer, then they may have claimed and verified…

Do you have the Story points field in the Field Configuration and on the screens used for the Initiative issue type?

Hello @sd nayak Refer to the Jira Cloud REST API documentation. Workflows APIs https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-workflows/#api-group-workflows Workflow Schemes APIs https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-workflow-schemes/#api-group-workflow-schemes

On the Rule Details page for the rule there is a checkbox labeled: "Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule." You need to have that box checked to enable the rule to run when the Epic's story points value has been changed by the…

Hello @Gal Fatal There is currently no native function to restrict the issues in the Create dialog. If the issue type is available in the project and is an Epic or standard issue type, then it will be available. There is a change request to enable restriction of the issues based on the user/role. You can add your vote to…

I apologize for providing an incorrect answer. I did not make note that you said you are working with the Product Discovery product. I have not worked with that product yet. I have not found anything yet that specifically talks about the Automation for Jira user and the Product Discovery permissions, nor the "addins" role…

Hello @Sandeep Kumar Welcome to the Atlassian community. It appears that you got to that search screen by selecting the Issues option among the navigation options for a Project. To get the full scope of export options you need to go to the search screen available as "View all issues" under the Filters menu.