Ignacio Pulgar Expert

Besides the change proposed by Gabrielle, I'd suggest changing status not in (STATUSes THAT DON'T matter) with statusCategory != Done That change will probably match your needs provided the statuses you are using were well categorised- and make your JQL query more readable and easier to maintain.

The most similar thing I've heard of is this free addon: https://marketplace.atlassian.com/plugins/whoslooking-connect/cloud/overview It is not supported by Atlassian and it is on Beta phase, but has collected a really good score on user votes. A complementary way of keeping track of issues on which your users are actively…

This diagram might also help you.fields_diagram.png

The addon's name is JIRA Timesheet Report and Gadgets, and can be found here: https://<your-company>.atlassian.net/plugins/servlet/upm#manage/jira-timesheet-pluginBoth gadgets are available for free, but there are some other features that require you to buy a license.We use this addon (free version), but had to enable it…

There's a specific label for tagging issues related to said plugin. You can find all available documentation here: http://www.jiratimesheet.com/wiki/Overview.html If you don't find the answer there, send an email to the developer: azhdanov@gmail.com

I'd use quick filters. That way, you can show only issues matching your desired conditions in one click.

I would suggest: * Configure the board's Columns so that the last (most-right) column contains two final statuses, ie: Done & Abandoned. On dragging an issue from the board, two landing status areas will be displayed in the last column so that you can drop the issue into the status you wish. * Modify the board's Filter by…

A better set JQL for the filter subscription would be: updated > startOfDay(-1) being executed everyday at 00:01 hours, as that way you always cover the full day and, besides, avoid the risk of suffering a delay that affects the results.

By the way, you can decide the fields you want to be sent by modifying the columns shown on the 'filter' tab, displayed in the menu on the right from the browse issues interface (Issues > Search for issues).

The JQL in the filter subscription is executed one time for each user subscribed to the filter. This means that a generic filter will send to each user different results, based on their specific Browse Project permissions. Try subscribing to a filter with this JQL to send it everyday at 23:58: updated > startOfDay() So,…

Hi Manuel, You have several options: * Create and save a JQL filter and subscribe to it with the periodicity you need and remove your username to whatever roles that trigger so many notifications (be careful to retain the permissions you need!). * Create a new project role, add it to the permission and notification schemes…

I think that email notifications on JIRA Cloud are automatically set to show the diff.

Maybe it was caused by this incident: http://status.atlassian.com/incidents/ng47t3pmyw6y

+1 to this feature request

Have you tried using the 'Fields Required' workflow validator of the addon Suite Utilities for JIRA?

Assuming you just want that user to be shown all issues currently assigned to them, it would be easy to show the date in which each of those issues had been modified in any way, despite of the fact that it is not the same than the date in which the assignment occurred (it will be the same date if the last action performed…

Could you elaborate more on the gadget approach?

* Go to Issues > Search for issues * select advanced mode and type this JQL: component in ("name of 1st component to remove", "2nd component", "and so on") * click on the button [...] from the top-right corner > bulk change X issues * select Edit operation, then Components, and finally set the field empty (None).

Good point! I usually forget to include EMPTY when it is required Thanks and regards!

Try adding this to the board's filter: ... AND fixVersion not in releasedVersions(ABC) ... where ABC is the project key. More info about releasedVersions() function:…

Same error here.

+1'ed

Cool :)

Oh, and that name change will be automatically reflected on all workflows using said status.

Have you tried looking for the status named "XYZ" in the Statuses view?From there, you can Edit its name back to Done, not mattering whether the wizard screen prompted to your colleague or not.

I agree admin privileges should only be granted to people who know what they are doing, but knowledge on how to use JIRA is usually acquired by trial and error, and most companies lack expert users when they started using this tool...

Alternatively, on Cloud, you can reach the Statuses page by modifying your company name in the following URL:https://YOUR_COMPANY.atlassian.net/secure/admin/ViewStatuses.jspa

Login with a user account with admin privileges. Press the dot key '.' Start writing Statuses and click on it. Find the status name you want and click on Edit to be able to change its name.

A site admin, I mean.

If you are a JIRA admin, you can login as the user to peform actions on their behalf: https://confluence.atlassian.com/cloud/log-in-as-another-user-776994835.html