Comments
-
You're welcome. Please mark the answer as Accepted to help other community members find the posts that include solutions.
-
Is this automation for issues in a Company Managed project or a Team Managed project? Do you want the parent to transition to In Progress if any one of its children transition to In Progress, or do all the children need to be In Progress? You said the rule doesn't run anything. The Audit Log for the rule should at least…
-
Hello @cullen Welcome to the community. In Service desk there is the concept of "agent" users and "customer" users. "Customers" in your case would be the companies to whom you provide service. "Agents" are your team members who work on the tickets. The issue you references concerns how to make the Queues visible based on…
-
Hello @Collista Lewingdon Did you try moving a Sub-task to In Progress? And try moving a child issue of an Epic to In Progress? What is shown in the Audit Log for the rule when it executes? Are the results different depending on which type of issue you change? Why do you have the "And:Sub-tasks match Status='In Progress' "…
-
Right, but ... The card in @Michael Harrison 's image is for an Epic, and it does not show the Epic Name. In my Jira Cloud Free instance the only time the Epic card does not show the Epic Name is when the Epic is in a Team Managed project. For an Epic card in a Company Managed project in my Jira Cloud, the Epic Name is…
-
Hello @Steve_G I advise you to not pursue this as it appears that the Epic Name field will be phased out in the future. Refer to https://community.atlassian.com/t5/Jira-Software-articles/Upcoming-changes-to-epic-fields-in-company-managed-projects/ba-p/1997562
-
Try adding an action to Re-fetch Data after the action that Assigns the issue. I used the Log Action in a rule to print out the Assignee after using the Assign Issue action. The Log Action printed no value. I added a Re-fetch action after the Assign action, and then the assignee info successfully printed.
-
try this [~accountid:{{issue.assignee.accountId}}] There needs to be context (issue) from which Assignee can be extracted.
-
Hello @Joshua Cumblidge You said you have automation to assign a user during a transition. Do you mean you have customized a workflow transition to include updating the Assignee, or do you mean you have an Automation Rule? Can you show the details of the workflow transition or Automation Rule that is doing this work?
-
Hello @Kelley Henderson Comparing what you pasted above and the post you referenced, your rule does not include the Branch/Related Issues/Parent component. And what is the point of your IF component?
-
Hello @aya nayman Here are a few posts that concern copying data from an Initiative type issue to a child Epic type issue with automation. https://community.atlassian.com/t5/Jira-Software-questions/Copy-field-from-Initiative-to-Epic-using-smart-values/qaq-p/1763373…
-
Hello @Igor Morduhaev Welcome to the community. Would you want to consider the work on the issue to be completed for purposes of closing the story (and sprint/release/epic burndowns) if the testing was not done? If so, then I would say the testing should be separate stories. Do you want to be able to estimate in story…
-
The architecture for Team Managed projects came long after the architecture for Company Managed projects, and the intent was to make a "simpler" project and also enable Project Administrators to have more control over customizations. Atlassian is working to reduce these differences in Epics between these types of projects.…
-
Good find!
-
History can be sorted by the dates of the events, and it includes all events. You might want to take a look at the third party apps that provide additional functionality for interacting with issue history. https://marketplace.atlassian.com/search?hosting=cloud&product=jira&query=issue%20history
-
No, creating projects is not part of the Advanced Roadmaps functionality.
-
Hello @Angana Patel You are correct - we were not talking about the same thing. I did not fully understand your question. It looks like you are correct and the feature is not available in Jira Cloud. I do not have any additional knowledge to share.
-
Hello @Motta-DAFC Can you provide more details on what you mean by "not linking correctly"? What steps are you executing and what do you see as a result?
-
Unfortunately I have not yet found any posts where a user was trying to copy the value of the Team field from a trigger issue to a related issue in Automation. And I don't have access to a Premium subscription to experiment with this more myself. The only other option I can think of would be to use the Send Web Request…
-
Team Managed projects are not available on Jira Server. The original poster tagged the post as "cloud" and "jira-software-cloud". If you are not using the same hosting type as the original poster, in the future I would recommend that you either mention that in your comment, or if you have a question on the same topic then…
-
Are you working with Jira Cloud or Jira Server/Data Center. I work with Jira Cloud, and the only time Epic Name is not displaying on the Epic cards is when those Epics are part of a Team Managed project. The Epic Name doesn't apply to Epics in a Team Managed project.
-
Did your Automation Rule fill in the Epic Name field when creating the Epics? If it did not, then that would be the reason "undefined" shows in the cards where the Epic Name should show.
-
Hello @sherri_nc Are you working with a Team Managed project or a Company Managed project? Are you a Project Admin for the project or a Jira Administrator? The path forward depends on the answers to those questions. For a Company Managed project, the next question would be does the custom field already exist in the system…
-
Hello @Valerie Capasso The number does not indicate the hierarchy level. The hierarchy level is determined by the position of the issue in the list. Refer to https://support.atlassian.com/jira-software-cloud/docs/configure-custom-hierarchy-levels-in-advanced-roadmaps/
-
Hello @Michael Harrison Welcome to the community. Without more information/screen images I'm not able to provide any feedback on your situation. What do you mean by "that's not allowed" in your scenario? You can't add the field to the card layout?
-
Hello @colin docherty Welcome to the community. Can you provide a screen image of the screen you are viewing?
-
Hello @lapacquah_bryant Boards display issues. There is not a built in issue type called "Automation for Jira Epics". Can you clarify what you mean by "Automation for Jira Epics"? The "undefined" label you see on the cards means that there is some field being displayed for those cards that is not defined for the type of…
-
1. Yes, Team Managed projects are available only in Jira Cloud. Company Managed are also available in Jira Cloud. The functionality of Team Managed and Company Managed projects is similar but different. Team Managed projects are intended to be stand-alone and managed by the Project Administrators. Project Admins can create…
-
Hello @Shelby Dziwulski Welcome to the community. You cannot change a project from Team Managed to Company Managed or vice versa. You have to create a new project of the other type and then move the issues to the new project. Refer to…
-
User Administration for Atlassian Cloud products allows you to remove the user's access to a product (such as Jira), suspend their access, remove them from your site, deactivate or remove their account (if it is a managed account). What you can do depends on your level of administrative access. Below are some articles that…