Comments
-
i guess you could if you have an app that allows you to add scripts to the workflow that checks when the issue was created, but that seems to be a lot of work to get it working. Your other option would be to create a new issue type with a new workflow and "retire" the existing issue type, but if it was my environment I…
-
There is, you would have to use the lookup issue action, and then use the lookupIssue smart value to group them into a single notification. You can find out more information about the list function here.
-
Yes, you can use automation to do this. Create one that runs on a schedule and use a JQL like this to get all the issues: sprint in openSprints() AND updated < -5d Your automation would look something like this:
-
Currently you have to link form questions to a Jira field in order to do it, since forms currently do not have a REST API. The API is scheduled to be released in Q1-Q2 2023 according to the public roadmap.
-
You can learn more about the different roles in a JSM project here.
-
The short answer is no, in order to transition a JSM request you have to be an agent in that project.
-
You could try this regular expression, I used a version of it way back in the days when I did a lot of Perl scripting: <span>(?</span><span>x</span><span>)</span> <span>.?</span> <span>|</span> <span>(</span><span> \\</span><span>2</span><span>?+</span> <span>(</span><span>\\</span><span>1</span><span>|^.)</span>…
-
It is because the rendering for that field is set to default instead of wiki style. You can change the renderer if you go to Project settings > Fields and edit the field scheme. Then locate the field and click on Renderer to change it.
-
Yes, the development information does show build status according to this KB.
-
Hi @Daniel Malament, Welcome to Atlassian Community! No, you cannot comment on things on the Dashboard, it can only be done from within the issue itself. If you also have access to Confluence you could create a page in there and add data from Jira to it and then use the inline comment, but you would not be able to do it in…
-
That is part of the new Risk summary that was added to Change requests. So in order to that function to work you have to add the field Affected services to the screen used by the issue type used in this case. Check out this article to learn more about the new Risk insights panel.
-
The workflow scheme is available if you go to Settings > Issues, and from here you should see it. What happened when you edited the workflow was that you where directed to Settings > Issues > Workflows, and once you saved it took you back to project settings.
-
No, as far as I know there are no free apps that will do this.
-
Correct, but it is a better way of manage the schedule than having to update an automation. And you can use the override option in the scheduler on urgent days off and other things.
-
Soon you would be able to use the on-call schedule in Opsgenie for the auto-assign, this feature is on the schedule to be released in Q1 2023.
-
Hi @Peter Arbaugh, Welcome to Atlassian Community! At the moment team-managed projects only support a single board, in order to create more then one board in a project you have to use a company-managed project.
-
Hi @rwheeloc, Welcome to Atlassian Community! The membersOf() function only works on groups, not the new Team feature that you find under People. So what you can do is create a new group and then your search with membersOf() should work.
-
You can share your plan either as a link, embed, Confluence, CSV, or Image, just click on Share as up in the right-hand corner.
-
The reason is that when you do it from the portal there is a function that adds the user to the participants list. There isn't anything corresponding on the backend view so you would need an automation for it. The web request would be using the users end point to get the accountId.
-
Hi @[deleted], Welcome to Atlassian Community! In order to add the user to request participants you have to get their Atlassian Id and use the advanced option to do it, similar like this: In this case Manager is a user pick field. In your case you would have to do a web request to the API in order to get the Atlassian ID…
-
Confluence does have an End of the week status update template that you can use, and together with automations you could create these automatically every week.
-
Hi @Jonty Yamisha, Welcome to Atlassian Community! You may want to take a look at Atlas from Atlassian, it is a new product that allows you to give status updates every week, and it will send out reminder to do that as well.
-
Hi @steve dudek, Welcome to Atlassian Community! Blocked reason is not a system field so someone created that as a custom field. My guess is that this field is on a transition screen when you move an issue to that status.
-
Make sure that all the fields you are editing is on the screen that is used for editing issues. Even if those are system fields, if they are not on the screen, automation will not be able to make changes to them.
-
Hi @Salma Sahnoun_Creativas_, It was the auto spam filter that moved your post into moderation. I have moved it back for you. The spam filter has improved over the years, but sometimes it can be too broad.
-
Another option to having a separate workflow is to use automation to set the epic status to done.
-
Currently that is not possible, once you have Jira admin permissions you have permissions to make changes to everything within Jira. Atlassian is working on a more granular admin role, and it currently on the roadmap to be introduced sometime in 2023.
-
The short answer is no, you cannot customize that message.
-
JWM is still part of JSW, no changes has been made to the billing. Please see this question as well.
-
Hi @Viviana Paola Gómez Paneso, Welcome to Atlassian Community! Currently Epics have two statuses, one is the workflow status and the other is the "hidden" epic status. In order to remove done epics from the backlog you have to change the epic status to done. If you right-click on them you should see an option to do that.…