Walter Buggenhout Community Champion

You only need to check this option if you want to let your automation rule be activated by another automation rule. From what your describe, I cannot see why you should need to check this. Your automation will run every time an issue is created in your project (that is what the Issue Created trigger (the first step in the…

Since you seem to be on a standard plan, the best way to do this may be to add the rule in each project separately. Yes, that means you have to configure it 3 times, but you have a limited number of rule executions in a standard cloud plan. Rules inside a single project are not counted towards that limit are not counted…

Hi @Barış Özer, A setup like this should do the trick: The condition (the second step in the rule) is a Field Value condition on reporter. In steps 2 and 3, just replace the reporter and assignee with the values you need. Hope this helps! 

Hi @Noriko Kawakami, If all goes well, when you edit a workflow scheme and click add workflow, you should see a dialog that looks like this: The next button to continue should be at the bottom of that screen. If it is not there, that may be a temporary glitch on you site, it is definitely unexpected behaviour. So try again…

Hi @Ashish Gireesh, You are probably seeing the effect of the changes announced in this community post. It does describe what was planned and currently rolled out. Hope this clarifies!

Hi @Rhys Christian, Having a central team concept across the board feels like filling a major gap for a company that has "unleash the potential of every team" as its mission statement. So very happy to see this major step towards that taking place. Since the concept was missing in the past, however, nearly every…

Hi @rakesh10, I am not sure what roadmap you are talking about. If you are on a premium plan and using advanced roadmaps, following these steps should let you create your roadmap from the kanban board: * Navigate to Plans > Create Plan * On the screen that appears, give your plan a name, select Boards as your issue source…

🥹

Hi @David Pleşu, Yes, your observation is correct. When sharing a filter with a group, you can only select groups you belong to yourself. That is most likely the reason why you don't see all of them here. Hope this clarifies! 

Hi @Callum Anderton, The list view you describe is a feature of Jira Work Management rather than Jira Service Management. But apart from that, you observation is right: the grouping (by assignee) does indeed work at task level and ignores the assignee at the sub-task level. That seems to be the way it is designed. It is…

Hi @Kevin Dickson, When you make the description field required via the field configuration of your project(s), you will be forced to fill out the field when you create an issue, even when you create an issue from the roadmap view e.g. Jira will show the create issue dialog when you try to create an issue inline there, so…

Hi @rbalamu2, What kind of team are you referring to? Is it an advanced roadmaps team? If so, did you make it a shared team or is it specific to a single plan? The team custom field only displays shared teams, so that would be my first candidate as to why it is not visible in Jira. If that is not the issue, do provide a…

Hi @David Fang, When you use the cloud to cloud migration assistant to migrate date between cloud sites, you will be presented with the following choice about user migration: If you choose to migrate users and groups separately, that will ensure that historical data (who created, update, commented on an issue ...) is…

Hi guys, While I do welcome the change, how come a selected team in JQL is not simply displaying the team name, but an impossible to read hash? We see the same with the Advanced Roadmaps team, but there it is a number that is being displayed. It would really be very valuable if that could be fixed before rolling out the…

Hi @[deleted], No, you are not missing anything. Your observation is correct: the hierarchy is strict and you cannot skip any levels there. Hope this clarifies! 

Hi @mark.hiblong and welcome to the Community! In most circumstances, moving a ticket from the backlog to the board is actually a status change. The columns on your board (including the backlog) are essentially columns mapped to an underlying status. If you look into the history of status changes, the moment when an issue…

Hi @admin-nwalter, Building further on that use case, you should be able to achieve what you want by referencing the value of your custom field and counting down 5 business days like this: {{issue.Customdate A.minusBusinessDays(5)}} Hope this helps! 

Hi @Petar Cvetanovic and welcome to the Community, You can add business days to your start date like this: {{issue.Start date.plusBusinessDays(10)}} issue.Start date is a reference to your Start date custom field. Just apply the same logic for your other milestones, replacing '10' with the appropriate number of business…

Hi @Syed Muhammad Ammad Mansoor, Verifying your domain just does 2 things: * Verify ownership of your company's domain * Claim the user accounts in that domain It gives you / your organisation the following benefits: * More control over the Atlassian accounts on your company’s domain – those accounts become managed…

Hi @Allan Pedersen and welcome to the Community! If nothing changed on the issues, maybe someone changed the description of the link type centrally in Jira. Issue link types are managed in Jira Settings > Issues > Issue linking. An issue link has an inward and outward link description. If that is updated, that will reflect…

Hi @Luke Simms, It may be worth having a look at who is configured as the owner of the automation rule that creates the ticket. You can verify that in the rule's details. If anything goes wrong with an automation rule, an email notification is sent automatically to the rule owner. Maybe that alone may be enough to cover…

Hi @Bill Thang, Let me start by stating what you should not do: move the original ticket. Apart from other settings, JSM projects tend to have different access settings. Moving a ticket to a different project usually means it disappears for the customer, which means you lose the line of communication with your customer.…

Hi @Aleksandr Ganiyev, No, you cannot add additional navigation items there. The options you see there are built-in features that you can toggle on / off in Project Settings > Features. The items you are listing as things you would like to add seem to be at a different hierarchy level in your Service Desk setup.New Server…

Hi @[deleted], Happy to see you've made progress since you started this. Since you are trying to create a structure that is not natively supported in Jira, you'll have to be very rigid regarding the way you set up relations between issues. Your observations are correct: if you add a task to an Epic, it will automatically…

Adding to what @Benjamin says, click on the name of your field type of document in the view you captured in your screenshot. In that screen, it is possible to add an alias to the actual custom field in Jira. By editing it, you may very well find out that the custom field is known in Jira under a different name. That may…

Hi @[deleted] and welcome to the Community! The agile hierarchy preset uses Jira's default issue hierarchy, which is: Epics > stories / tasks / bugs / ... (all standard issue types) > sub-tasks And so indeed, you cannot add tasks below a story. They are both on the same level. If you want to create a structure where tasks…

@Lara Sousa , regarding your comment: To be more specific, the epic has a label that I would like to replicate for all tasks that are associated with it.I've already managed to configure an automation for when creating a new task, to copy this label from the epic, but for the already existing tasks, I couldn't. Do you know…

Hi @Lara Sousa, Yes, you can copy fields from an epic to all related issues with automation. You always need a trigger to start your action and that can be many things, as you can see here (the list below is not even complete yet): After you specified the desired trigger, all you need to do to copy the desired field to…

Hi @Jared Holliday, If you want to introduce something like this, it will always be a pretty subjective metric. What is difficult for me may very well be a walk in the park for you or vice versa. Before you try to introduce a metric like that, ask yourself how it would help you get things done more effectively. In one of…

Hi @Renata Gabardo and welcome to the Community! Unfortunately it is not possible to search for the start or end dates of sprints in JQL. There is a feature request for that type of functionality that you can track here: JRACLOUD-72007 You can search for issues that changed to a specific status between two dates, but you…