Comments
-
It is not just in automations that you have to do this. Anytime you are doing a JQL that you want to exclude a label or component from you have to include when the label/component is empty.
-
It is because you are searching on labels. When you do that you either have to include issues that do not have a label like this: duedate < -30d AND (labels != Post_Survey OR Labels is EMPTY) AND resolution was "done" The other option is to negate the label like this: duedate < -30d AND NOT (labels = Post_Survey) AND…
-
Well, if the sprint has been deleted then there is not much you can do unless you have a backup of your instance.
-
You would add this to your JQL to get issue that are due 7 days out: due = 7d Another option to do it is to use smart values to see if the due date is 7 days out, similar to this automation that I have that sends a reminder 90 days out: The reason I'm using smart values is because the due date is not required and there are…
-
Hi @magaly, Welcome to Atlassian Community! If you go to Reports > Sprint Reports do you see the sprints that disappeared in the dropdown list? If so that would mean that someone closed your sprint when they closed their sprint. This can happen since sprints are not project or board specific but can be used in any project.…
-
What type of change is it? Where in the workflow are you? If you selected Standard change or Emergency change it will move the change to Awaiting implementation, but if you used the Normal change transition it will end up in the Review status. You would have to create a service and add the approver group if you have not…
-
Forgot to add that by default the approvers are populated based on the service that has been selected to be affected by the change. If you do not use services you would have to change the Authorize status so that the Approvers field is used instead, that way you can control how approves it. You can learn move about change…
-
Hi @Jordan Pritchard, Welcome to Atlassian Community! If you are using the default workflow for changes you will see that there are three transitions available depending on what type of change it is. Normal change is the one that you want to use if you want to have someone approve it before the change is implemented. This…
-
Hi @Madeline Chapman, Welcome to Atlassian Community! There are two different release tracks that you can be on on Cloud, either continues track where changes are added as soon as they are available or bundled track where changes are rolled out as a group once a month. You can check which one you are on by going to…
-
Every project template has a default workflow attached to it, that doesn't mean that you can make changes to it. The only thing you have to consider when doing it is if you have automations that expect certain statuses or if the workflow is shared across multiple projects. Another thing is that you should never rename a…
-
No, any app that you want to use has to match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses must match exactly. If you check the pricing tab in the Marketplace listing there is an FAQ that explains this.
-
You can do this with smart values, just get the created date/time and then use {{[date].[dateformat]}} to get the hour and minute the issue was created. Here is an example of a round-robin automation I have where I log the hour and minute in the log:
-
You cannot use automation to block or lock a user from creating an issue. Automations runs after the issue is created. You would need something like Scriptrunner or other Marketplace apps that extends the workflow so you can add a condition to prevent the user to submit the issue. When I was on Jira DC I used Scriptrunner…
-
It should not affect anything, I have made that change and added other statuses/transitions without any issues. The default setup only have an automation that is dependent on waiting for support and waiting on customer so the status is automatically changed when either an agent or the customer adds a comment.
-
Hi @Ned Lindau, How do you edit the announcements now that it has moved under its own pill? And do agree with @Andy Gladstone and others that it should still be its own section. Being sticky is one thing, but if users do not have an habit to look at the announcements, or not using the home page at all, they may miss…
-
You cannot limit the automation under rules details to a specific category, but you can add a JQL condition in your rule that checks if the issue belongs to a project in a specific category like this:
-
This is expected, if you look at the documentation for the WAS operator it states that it only support the fields Assignee, Fix Version, Priority, Reporter, Resolution, and Status. Status category is not a field on the issue, that is linked to the status.
-
Your JSM project can only have one request type that is used for incoming emails. The same thing applies to email address, the JSM project can only have one. You can work around it by either using email aliases that forward to that single email address or use automation that parses out email requests that are coming from…
-
What you are seeing is because you have at least two different workflows in the project and the initial status for one of the workflows is linked to the in progress column like this: In my case I have tasks and stories in the project and they have different workflows. If I click on create issue in the To Do column it would…
-
You have the option to edit the title so that you can reorder the pages within the space and set new homepages. I am not sure if there is a way to change the alignment, but that would be a good suggestion to be added to jira.atlassian.com
-
This is what I would do, I would add a log action that has the value of {{issue.EIS Group}} so you can see what the format looks like. You can then from there use smart values to remove/replace characters so that if fit with what AQL is expecting. I have an automation that gets approvers based on department that is…
-
I would also look at the status mappings to the columns, maybe someone renamed statuses or changed a workflow that affects these projects.
-
I would check the filters that the board is using, under board settings > general. If you go to the project and look under Issues, do you see all the active issues there?
-
Here is a comparison of features between JSM Cloud and Data Center.
-
You could do something similar in Data Center, but it would require that you set up a service catalog in Assets and then include that in the automation that sets the change risk. On Cloud there is a service registry where you can set the tier, and that tier is used to set the risk. Everything else is just two custom fields…
-
Are you editing the home page for the space you are in? Is so, then the title will aways be replace by the space name. Currently there is no option to display the page title of it is set as the home page. There is a suggestion to change this, see CONFCLOUD-74029.
-
Btw, we decided to turn off the KBs in the portal because of the way they are displayed. Instead we opted to use Confluence as our portal and directing users there because we can then have both KBs, requests and other information on a single page. Yes, the requests still link back to the portal, but it does allow us to…
-
Hi Rachel, Those topics are coming from the Knowledge base and are categories that have been created in there. You can then add your KBs to those topics. If you go into your project and click on Knowledge base you should see it there.
-
This is expected. Sprints that are created in one board will only be visible in other boards if those boards shows issues that have been linked to the sprints in the first board. So in your example it means that on the second board you are seeing the current sprint and the other one because you have issues on that second…
-
Hi Richard, One option would be to use filter subscription and have that send out an email to the agents on a weekly basis. Another option would be to use automation to send a list of requests to each agent, you can use the list smart value in the email message to list all the issues.