Jack Brickey Expert

i believe it updates immediately as required based upon changes. I see you accepted my answer. Does that mean your issue is resolved? If so can you update w/ the reason? Maybe it just started working? :-)

my guess is that you do not have a transition from the current status to the "Start Progress" status. Make sure you workflow has the necessary transitions to support the automation.

If you are on server I believe there is an audit log you can access that captures changes. In Cloud you don't have access to the logs. Either way I would suggest contacting Atlassian Support

This is not configurable. At least I have never seen a place to disable. Might I inquire as to why you wish to do this?

@Prasad Andrews , I just responded to you in your other post. Best to discuss there.

can you click on the "show details" for the not executed and error automation attempts. Generally the details point to where the issue is. feel free to share so that we might assist further.

I assume you have the Customer Notification "Organization added" enabled as this results in an email to all users in an organization when someone in that org creates an issue. I never enable this as it results in a lot of unwanted notifications at least for all current customers I have. Assuming the above is accurate, my…

you might want to view the following suggestion and vote/watch. There is a suggested work around that should work well using Automation. JSDCLOUD-3374

You will need edit permissions so have your admin give you those permissions and then you can edit the description.

I don’t believe there is any field set by default when this happens, I may be mistaken. There is Requestor field that could be used to capture the agent.

As @Alexander Pappert indicated it is step 3. Hit the back button or cancel and start anew. 

The admin could create a temporary transition or a transition that is restricted to them or a small group. Often an Approval workflow will include a “bypass” transition that allows the admin to skip the approval for various reasons/conditions. If you have a condition where sometimes approvals are not required then the…

My bet would be it didn’t get Published but you say you did. The image seems to say it needs to be. Please verify by viewing the workflow rather than editing. The other thought would be indexing but for cloud this is automatic. Where are you viewing that is showing the old status?

Which Automation addon? You will need to look at the documentation for the addon you have. I know that Automation for Jira has a function for parsing comments.

You need to remove the user from any group that has permissions to the project. You can do this by creating a new group for the project and exclude them from the group or you can remove them from the group that currently has access to the project. Keep in mind that the later likely will impact them in other projects.

When doing bulk updates there is a checkbox to uncheck so that Notifications are not sent. It is the final screen before execution. Just have to scroll down.

You need to either have the admin close it or have them add a “cancel” transition to the ‘closed’ status. It should also include a post function the set the Resolution to ‘cancelled’ or similar value.

Make sure the user has Schedule permissions - project > project settings > permissions > schedule

You can’t change the system field names. And why “retainer” which is something that holds something in place while an epic, in scrum terms, is a collection of stories.

What is “multiple Assignee “? This sounds like a custom field. If your gadget is triggering on Assignee then it should reflect all issues by Assignee. If the multiple assignee is a separate field it isn’t related to Assignee and will not be considered.

You can and should view this in the backlog when creating the sprint. Once you have added issues to a future sprint and added an original estimate then you can click on the ellipses at the top of the sprint and view the details. 

2 dimensional gadget. example...

i don't know of any progress bar method. keep in mind that unless the workflow is relatively simple this could become messy. You can certainly show the status of all issues and sort the list by status. you could consider say a pie chart by status or you could look at the 2D gadget by maybe assignee (Y) and status (X).

for me there are two gadgets I use for this: * Created vs. Resolved gives me a 50K foot view of whether a group or individuals are keeping pace w/ the incoming or not. * 2D gives me a 10k foot view of how Assignees are doing by mapping assignee to Y and status to X. you can create filters as required to align w/ your needs.

are you using Confluence? If so go to Confluence, click on the search and enter "retrospective".

Just my opinions here... I would set the fix version on every issue regardless of issuetype where the work done under the issue resulted in actual changes directly to the release. If an epic spans multiple releases I would add the final fix version w/ a comment explaining some work was done in previous versions. A JQL…

you might wish to reach out to their support and inquire. Maybe this field is part of their addon, not sure.

correct. 

Yep good tip

Without an addon it is challenging at best where sub-tasks are involved. if your parent tasks are known and few... project = ABC AND "Epic Link" = Abc-123 OR parent in (abc-124, abc-223, abc-321...)