Ignacio Pulgar Expert

Yeah, Nic is absolutely right, and I agree on the fact that temporarily adding the resolution field to the edit screen is a much easier and faster task. You shouldn't forget to remove the resolution field from the edit screen after fixing the resolutions. Also, do not forget to ensure that all transitions that go to the…

I have edited my initial answer to avoid confusion.

Sorry, my fault: You need to perform a Transition operation (not an Edit one), from Closed to Closed again (or back and forth) ensuring the workflow transition you are going to use had a post-function which automatically fixes the resolution.

Have a look on how to automatically set a resolution in your workflow: https://confluence.atlassian.com/jirakb/resolutions-are-not-set-225122076.html

Look at this other answer on how to remove that restriction: https://answers.atlassian.com/questions/46686099 (Edited: Despite of the title of the question "Change Security Level", the actions described in my linked answer have nothing to do with security levels)

By the way, you should make your workflow set a resolution on transitioning an issue to the Closed status. That way the Created vs Resolved chart (as well as other built-in gadgets, charts and functionalities) will work as intended. 

(Edited) Hi Thomas, That's not possible. The best approach would be performing a bulk-change Transition operation to set a resolution on all issues in Closed status, by using a workflow transition previously set to set a resolution. Best regards, Ignacio

I confirm there's a backlog section on Card Layout section for showing there up to 3 extra fields, including custom ones.

Go to your Kanban board and click on the "Board" button on the top-right corner > Configure. Then, click on the option "Card layout" on the left side. Select your custom field in the dropdown menu and click on the Add button.

You can better create a suggestion here: https://jira.atlassian.com/secure/Dashboard.jspa

Try setting this JQL in your board's filter: project=<KEY> AND (status in (New,"In Progress") OR (status=Done AND status CHANGED TO Done AFTER startOfWeek())) ORDER BY Rank ASC Where <KEY> should be substituted by the key of the project which issues you would like to show in your board. You can add multiple date conditions…

I don't think that's possible. You can create an independent group for that and add the desired users there. That way, you can have full control and mind some exceptions.

Check my last comment. You can do so by saving all those JQL queries as your favorite filters and then, add the Favorite Filters gadget to your dashboard. This will require to save one filter for each change from one status to another one.

For getting the number of issues that had changed their statuses today, you can create a gadget in your dashboard in which your saved Favorite Filters will be shown together with the number of issues which that JQL return. In order to achieve this: * Enter Configure System Dashboard page. (press 'g' key twice and type…

JQL to get all issues which status had changed today: status changed AFTER startOfDay()

Cool solution! +1ed!

JQL to get all issues which status had changed today from "new lead" to "contacted": status changed FROM "new lead" TO "contacted" AFTER startOfDay() It would be handy saving this JQL as one of your favourite Filters, so that you can perform that search with a mouse click.

Have elaborated on my answer here: https://answers.atlassian.com/questions/33151280/answers/33151520I would have been clearer from the start, but my answer here was written through my mobile...

It is not posible without the help of a plugin or addon. Look for a plugin for your JIRA Server, and you will probably find a free solution. On JIRA Cloud, there's a free addon called JIRA Timesheet Report and Gadgets, which enables the convenient Project Pivot gadget.

It means that, as the workflow you are currently editing is active and in use by at least one project, then you have to make a copy of said workflow, do the changes you couldn't do when receiving that message, and finally set that modified workflow to substitute its previous version.

This document will help you getting the worklogs. Alternatively, you can just pay $10 USD / month (or $5 USD for up to 50 users) for the Time Reports addon.

Try contacting Atlassian Support, but they are not contractually enforced to assist you in this kind of request. If you cannot recover the lost issue from the daily backup, the issue has been lost forever. If you think (as well as I do) that JIRA should count with any way for recovering issues deleted accidentally, please,…

Atlassian is currently working on unifying all spread product accounts in just one through Atlassian Accounts. Hopefully, they will achieve good results soon, for a better user experience and integration among all their products.

Good point. Then, apart from the pid thing, I think the questioner is actually asking:* what can I use as a unique identifier for a given JIRA instance [within a Data Center]? And how can I get that identifier?

For the JIRA instance id I would use its base URL: https://<company>.atlassian.net For the project id, I would use the pid number. I guess there are more elegant (REST API) ways of getting them, but you can look at each project's id by hovering your mouse over their 'edit' option in administrator's projects…

Do you mean the base URL of your instance?

Do you mean through a JIRA Service Desk automation rule, or through calling the API?

It is possibly because of this: http://status.atlassian.com/incidents/p0ynlrgdhbmn

The post-function is currently called "Set Field Value to constant or Groovy expression".

Thanks, Nic! I will add it too.