Comments
-
Have you verified that you still have access to the project? Check with the admin inspect your permission status.
-
That is a user account used by automation for Jira so that it can run and execute rules. All actions within Jira require a user account so that is why apps use a user account to make changes.
-
i would i=expect it to work as it is. admins are special cases.
-
here are the API docs - https://developer.atlassian.com/server/jira/platform/rest-apis/
-
that would be consistent with my expectations.
-
I haven’t looked at using components in any automation rule however you should have an option to add to components not overwrite it. However, to be honest I’m still a bit lost. Are you saying that you have a user name production? I was thinking production was some sort of category or lifecycle milestone. If production is…
-
That is interesting. So are you saying that someone that does not have the aforementioned permissions is able to archive issues in the project? Are these users admins?
-
The two issues you speak of have a status of acceptance and the remaining time is non zero then I would expect them to show up to be honest. What does accepted represent? Is that the final status like done? If your ultimate goal is to ensure remaining time is always zero for any issue that is transitioned to accepted/done…
-
No, automatic reindexing happens pretty much in real time or nearly so. When I have changed custom fields in the past they change right away.
-
I wonder if using the Components field might work here? This field might be used to signify Production or other areas of responsibility. I’m not quite sure how you “assign to production” unless you mean someone in Production. here is a link to Automation docs - automate-your-jira-cloud-processes-and-workflows
-
You could use automation for this. Basically you’d want to trigger on issue updated check the assignee based on the assignee set the label. I would also likely check the label to see if it already has that label on it and if so skip it. This covert cases where you’re going around in circles resigning issues. Having said…
-
Correct in the cloud re-indexing is automatic
-
if that filter resolves to the issues you want to change then yes. to change the name of the filter click on the Details link then Edit permissions.
-
this is not possible today.
-
For what it’s worth, what I do for one of my teams is to create a triage queue. It is represented by any new unassigned ticket. My team understands that that queue must remain at zero. The entire team is responsible for reviewing that incoming issue Q triaging them and taking ownership to ensure someone is addressing the…
-
Likely the best option here is to create a JQL filter that represents all issues that you wish to move from to do to done. Then at the top right where are you find the… You will do a bulk edit operation.If you are not familiar with creating a filter please let me know
-
OK great I haven’t set up a subscription in a long time and I thought it was only daily or hourly but glad to meet your needs
-
Correct zero issues are meant to be assigned to a single user or to a user account not to a group
-
if you need a separate instance it will be a unique URL and subscription
-
I don’t use boards with my JSM projects however for business projects I know if you edit the workflow it will break the board. Business projects and possibly JSM projects require that the workflow remain simple as defined by the template. You could always create a kanban board via a predefined filter and set your location…
-
You will be prompted to map any issues in that status to an existing status. If there are no issues in that status then you don’t need to do anything.
-
Oh but wait. You can only do this at a frequency of daily or greater. So if you want to do it every 10 minutes which I would personally recommend against due to performance reasons then you need to turn to automation. trigger - scheduled (use cron expression) condition - JQL = assignee is empty action - send email
-
So what you do is create a filter first. To create a filter click on the search bar at the top and then advanced search. Then in that screen you will create a filter that meet your criteria something like this… project = abc and assignee is empty Then save that filter giving it a name. Finally click on the details link at…
-
What about other projects do you get the same behavior there too?I have to wonder if there’s some sort of automation let’s add in 30 days to the due date for some reason.
-
Is this repeatable? What if you reset it to June 11? What if you set it to some other date?
-
I recommend revoking access of the customer(s) when expired.
-
And the default user must be licensed. The idea here is that issues created by non-licensed users will be created under the licensed user account.
-
Precisely
-
I would probably create an epic with tasks and sub-tasks. Then create a manual automation rule to copy the epic and children.
-
This is good input. I have been using Jira for many departments where I work. As a result more folks are coming on board every week.