Trudy P Claspill Community Champion

I recommend this structure. Branch 1 handles the scenario where an issue has been added to an Epic. If the issue has been simply removed from an Epic then Branch 1 will be skipped. Condition 2 evaluates if the issue was previously associated to an Epic. If it was, then the subsequent branch will handle updating the issue's…

You need a separate rule to monitor for a change to the "Parent" field. You can make a copy of the existing rule as a starting point, and change the field monitored in the Trigger to Parent. The structure you have would then handle the update of Start Date for the issue's new parent Epic. Did you review the information in…

Hallo @Anton Preitsameter , Willkommen in der Atlassian-Community. In der Confluence-Anwendung gibt es keine Stelle, an der Ihr Passwort angezeigt wird. Das wäre eine extrem schlechte Sicherheitskonfiguration. Wenn Sie Ihr Passwort zurücksetzen müssen, sollten Sie die Option „Passwort zurücksetzen“ verwenden, die auf dem…

Hello @Priyanka Agrawal Welcome to the Atlassian community. For the case where an issue is removed from an Epic you would need to start with the Field Value Changed trigger and monitor the Parent field. With that trigger you get access to the {{fieldChange}} smart value, which allows you to access the value of the field…

Hello @Joseph_ Smitha _Cognizant_ Welcome to the Atlassian community. The answer depends on the configuration of your instance. Out of the box Jira doesn't prevent addition of subtasks to resolved issue. But your Jira administrators may have customized the configuration so that activity is prevented. Have you tried it and…

Hello @Shashi Singh (Shashi Singh) Does the user have access to Jira? - If not, you will need to contact the Product Administrator, User Administrator, and/or Organization Administrator to get the details of how that access can be enabled. If the user has access to Jira, does the user have access to see the content of the…

Hola @Gloriana Córdoba Soto , Bienvenido a la comunidad Atlassian. ¿Quieres deshacerte de tu aplicación Jira por completo para todos los usuarios que tengan acceso a ella? ¿O quieres bajar al plan que sigue siendo gratuito? Si desea deshacerse por completo de la aplicación Jira para todos los usuarios que tengan acceso a…

Hello @Ioana Neagoe At this time card customization in Jira Business/Work Management projects is a user-specific configuration. There is an unaddressed change request to be able to apply the customization at the project level so all users see the same. https://jira.atlassian.com/browse/JWMCLOUD-320

Will it always be in the format? # <space> days Just curious, if the field is always going to contain a number of days why was it not created as a Number type custom field?

2. Does the Feature issue type already exist for this project, or Globally? Go to the gear icon near your avatar and select Issues. Then select Issue Types. Is Feature in the list of Issue Types? If so, what number is shown in the Hierarchy Level column?

Hello @Reggie_Hicks The native Issue Type Hierarchy for Jira is Epic (level 1) |-- standard issue types (level 0) i.e. Story, Bug, Task |-- subtask issue types (level -1) An issue's parent can be of an issue type in the level directly above it, and its children can be of an issue type in the level directly below it. An…

You're welcome! If my responses helped you solve your requirement, please consider clicking on the Accept Answer button to mark your post as Solved.

Your custom field returned text, not a number. You can't use text in a math operation. It needs to contain only a number, or parse the field to get just the numeric content. Since you have defined it as a text field, what other text might you place in that field? Do you expect it to always be "# days"? Could there be some…

Wonderful! If you problem has been addressed and my responses helped, please consider clicking on the Accept Answer button above my response thread to mark your post as Solved.

Then the answer I provided should work for you. I was successfully adding an imported issue created in a Company Managed project to an existing epic in the same or another Company Managed project if I used either the Epic's key (ABC-123) or its unique numeric ID (12345) in a CSV field that I then mapped to the "Epic Link"…

Hello @Greg Clayton I attempted to use ORDER BY (ABC-1, ABC-2) and got an error message. I don't think that is valid syntax in Jira Cloud. Why not just use the native Rank feature to prioritize the issues? In a board screen you could drag and drop the issues to reprioritize them.

Hello @Hina Imtiaz Please review my last response. It is not possible to make an imported issue a child under an Epic as part of the CSV import process when importing to a Team Managed process. There is an unresolved change request asking for that to be supported. You will have to manually add the child issues to the Epic…

Hello @Daryl Marsh As a debugging technique, with you FOR branch can you add a Log action to print out the two smart values you are trying to use: {{issue.Story Points}} {{issue.customfield_10795}} This is to get confirmation that the fields contain the values that you expect. Please then share with us an image of the…

Yes, there is: https://jira.atlassian.com/browse/JRACLOUD-87232

Thank you for that additional information @Trevor Adams I have not been able to think of a work around for your situation. To see the Epics and Enhancements at the same level in the Plan, they must be at the same level in the Hierarchy. But that does, indeed, remove Enhancements from the issue list and add them to the…

Hello @Julian Ranger Welcome to the Atlassian community. If you have not enabled Anonymous/Public access to your instance then the Assignee can be set only to licensed users of your Jira instance. You could add a custom Status to the issue workflow such as "Assigned Externally" to indicate that an issue is being worked on…

Hello @Reggie_Hicks I think we need more information to answer your question. Is the user trying to change an existing issue from one issue type (User Story) to another issue type (Feature)? Is the user wanting to be able to create child issues under a User Story issue type, and have those child issues be named "Feature"?…

Is the destination project Team Managed or Company Managed? I was successfully adding an imported issue created in a Company Managed project to an existing epic in the same or another Company Managed project if I used either the Epic's key (ABC-123) or its unique numeric ID (12345) in a CSV field that I then mapped to the…

Thank you for providing those images. Can you go to the Board (vs. the Backlog) view, and click on the Configure Board option. Navigate to the Columns and Statuses configuration. Make sure that the Statuses are all mapped to columns on the right, not listed under the Unmapped Statuses area.

Hello @Rodriguez_ Emily Welcome to the Atlassian community. Can you provide a screen image of what you are seeing in the Timeline and in the Backlog, and a screen image of one of the issues you think should be displayed but is missing? Obscure confidential data.

Congratulations, @margarita.martinez ! Well done! And, welcome to the Atlassian Community.

Hello @xiaolin.zheng If you are referring to the Timeline that is available in the navigation area when you are viewing an agile board, that is the "basic" Timeline. i.e. That Timeline view can display only two levels of the issue tyep hierarchy; Epics and their child issues. It cannot display the lowest hierarchy level;…

@Florian Bonniec In Jira Cloud the "Parent" field is used to identify all parent/child relationships based on the Issue Type Hierarchy. Parent Link is no longer used.

Hello @Trevor Adams Welcome to the Atlassian community. To ensure we have all the information about your scenario: 1. In what type of project do your Epics and Enhancements exist? Get that information from the Type column on the View All Projects page under the Projects menu. 2. What type of board are you using; Scrum or…

Welcome @Marcos Defina ! We're glad to have you join us!