Trudy P Claspill Community Champion

Hello @Janarthanan Selvaraj Welcome to the Atlassian community. You can definitely have different sprints for the lowest level issues in your various Initiatives. Have you tried to do that and found that it did not work? Do you want to have different sprints in one project and be able to have multiple sprints active…

What JQL are you using? Where are you using the JQL? Can you provide an example of an issue that is missing (or appearing) inappropriately in the results?

@Devoloper Correct; extending the issue type hierarchy is available only in Premium and Standard plans. Martina indicated that the Premium plan is being used.

The last image indicates that you created a Software project. Which Project Template did you select to make that project? Did you elect to create it as a Company Managed project or a Team Managed project? That information should show at the bottom of the navigation panel on the left, in the same screen as you showed in the…

Thank you for that additional information. I found that this is related to the new issue transition experience, which I don't have enabled. https://community.atlassian.com/t5/Jira-articles/Now-GA-try-the-new-issue-transition-experience-in-Jira/ba-p/2734436#M14880 There is a change request about disabling this message:…

Hello @gyorgyolah In the post I referenced, the community helped me find the problem. So this solution should work for you. What issue event do you want to trigger this automation? - Should it run when the Epic is created, if the Epic has the Label value that indicates it is an Epic for a release? - Should it run when…

Oh, bother! When I manually create an issue in the project and leave the Assignee field set to "Automatic" it is assigning the issue to the same user. Initially that didn't make sense. There are no Components set for the issue, and at the Project level the Default Assignee is "Unassigned". And then I looked at the Create…

The native Request Type field is valid only for use in Jira Service Management projects. That field should not be included in any other types of projects. What is the project type for the project in the first image you provided in your original post? Get that information from the Type column on the View All Projects page…

You can learn about creating and saving search filters from the documentation here: https://support.atlassian.com/jira-software-cloud/docs/search-for-issues-in-jira/ You can also find free training materials concerning search filters and dashboards and many other Atlassian product topics at https://university.atlassian.com

Hello @Cassandra Hughes Welcome to the Atlassian community. What elements of the existing project do you want to reuse when you create a new project? - The configuration (i.e. fields, screens, issue types, workflows, etc) - The users assigned to project roles - The issue in the source project - The configuration of a board…

Hello @Trần Hưng Welcome to the Atlassian community. The Issues In Progress gadget will show the issues that are In Progress and assigned to the user currently viewing the gadget. You can create and save a filter to get the same results for a different status; i.e. assignee=currentUser() and status="To Do" You can then add…

Hello @고범석 Welcome to the Atlassian community. You can check for incidents and outages here: https://status.atlassian.com/ The Request Type field will show only the Request Types that are mapped to the Issue Type for the issue you are editing. What is the Issue Type of the issue you are editing? If you go to Project…

Hello @khushboo_puri The Resolution should only be set when the issue is transitioned to a "done" (green) status. When the Resolution field appears on a screen a value must be selected. You can't make that field optional. Why do you want to set the Resolution while the issue is being created? What problem are you trying to…

I did not find any mention of a new kudos feature in the latest weekly update: https://confluence.atlassian.com/cloud/blog/2024/10/atlassian-cloud-changes-oct-21-to-oct-28-2024 Have you checked to see if a new app has been installed that could have included the feature? Can you provide a screen image of an example of what…

Hello @Glenda Dixon Welcome to the Atlassian community. The tags on your post indicate that you are using a Free Jira subscription. Is that accurate? If so, you can't limit project access. The Free subscription doesn't support customizing permissions and product access. Refer to…

Not yet. I wanted to reach out to the community first, in case I was missing something that would be obvious to somebody else.

@Chi Am _Addon-Solutions_ Welcome to the Atlassian community. The filter for a Team Managed project's built in board cannot be modified.

Hello @Marcela Junyent I don't have a comment on your approach to schemes, but I did want to check if you are aware of the price changes that have recently been implemented for Assets in Jira Service Management Cloud. Assets are available only if you have a Premium or Enterprise subscription.…

Hello @Matthew Barber Welcome to the Atlassian community. With what type of project are you working? Get that information from the Type column on the View All Projects page under the Projects menu. If you are working with a Software project are you working with a Kanban board or a Scrum board? What type of issues are you…

Hello @Michelle Kramer Welcome to the Atlassian community. I don't think Jira Cloud has a native kudos feature out of the box, but there is at least one app that provides such functionality. Has such an app been added to your environment? Can you provide a screen image of one of those pop ups as an example?

Hello @gyorgyolah I have been working on a solution for this. The solution is not working on my instance, but it works for another user on their own instance. I opened my own community Question to ask why my solution isn't working. You can follow along with that here:…

The only entry in the History tab for each issue is the entry noting it was created by Automation for Jira. I love these problems where it seems that people are doing the exact same thing, and yet it works for one and not the other. :-D I'm open to other suggestions to accomplish this. I started exploring this because of…

Hello @S_ Morgan Welcome to the Atlassian community. Those are not fields that are created by Jira. Your Jira Administrators have added those as custom fields specifically for your environment. You will need to check with your Project Lead(s) or your Jira Administrators to find out the proper use for those fields.

Thank you for trying this out, @Bill Sheboy The actor for the rule is "Automation for Jira". I updated the Create Issue action to remove the JSON and set the Assignee field directly with a Smart value. The JSON shown is just the default text shown when you open that dialog and haven't entered your own code yet. I ran the…

Hello @josemaria.zolle What type of project are you using? With a Business/Work Management project you get a native board that is similar to Kanban but not quite the same as the Kanban board available with Software projects. However the business project board allows you to switch between column grouping types using Status,…

Hello @Martina Amui Welcome to the Atlassian community. It is not possible to extend the issue type hierarchy for a Team Managed project directly in the Team Managed project. But there is a work around. The work around is to create the higher level issue type in a Company Managed project, and use a Plan to link the Team…

Additionally, you don't need to use two Lookups to get the tasks under epics under an initiative. You can use the portfolioChildIssuesOf() function. issue in portfolioChildIssuesOf("{{triggerIssue.key}}") and issuetype in (Task,Story,Bug) Update the list of possible issue types to include all that might be children of…

Hello @Rafaella Sena Welcome to the Atlassian community. First I recommend that you print out the smart values from your Calculation into the rule execution log using the Log action to ensure the values contain what you think they should. {{lookupIssues.filter("status.category.name == 'Done'").size}} {{lookupIssues.size}}…

Thank you for clarifying what you meant by "I do both". I had misunderstood. When you drag a card from one column to another you are changing the Status of the issue. It is also possible to change the issue's rank during that move. The only way to prevent a user from changing the Rank of an issue is to remove the Schedule…

Hello @cl1motorsports What do you mean that you "did both"? Did you remove both the "Schedule Issue" and "Edit Issue" permissions for a user for a project, and that user was able to change the rank of an issue in that project? How are you confirming that the rank has been changed? I recommend that you check the rank using…