Ignacio Pulgar Expert

You might want to have a look at these addons: * EazyBI * Time Reports

http://status.atlassian.com/incidents/fxkmq87bs3hj

This is happening apparently to all Cloud instances. https://answers.atlassian.com/questions/46323784

Hola Patricia, La documentación relativa a a la configuración de email está aquí: https://confluence.atlassian.com/adminjiracloud/creating-issues-and-comments-from-email-779288896.html Creo que no se puede configurar para responder a un usuario inexistente, pero sí se puede configurar para que se cree una nueva cuenta en…

It would have been enough to divide by 5.0 instead of 5. int / int = int int / float = float

Go to: https://<YOURS>.atlassian.net/secure/admin/ViewStatuses.jspa Click on the arrow icons on the right side of every status to reorder them as per your needs. The order will be used in gadgets.

Could you possibly accept your answer?

You might also want to vote for this issue: https://jira.atlassian.com/browse/JRA-62208

Try this instead: https://<YOURS>.atlassian.net/secure/admin/CsvSetupPage!default.jspa?externalSystem=com.atlassian.jira.plugins.jira-importers-plugin:csvImporter

It's not just you: https://answers.atlassian.com/questions/39978780

Oh, sorry, I've found this page: https://productsupport.adaptavist.com/secure/Signup!default.jspa

My email is ignacio dot pulgar at incentro dot com

Thanks Nic & Mark, I've tried to register through Mark's URL, but there's no option for doing so. I've tried the 'Forgot my password' approach and, while the message about an email to reset my pass was being displayed, I've received nothing so far. I think I've never had a customer account on that Service Desk. May you…

Yeah, that's another possibility, and easily doable by opening and saving through a spreadsheet reader. The workaround of the foo issue is only better for editing the file through a text editor, like notepad++, as it would remove the need for intercalating any additional commas. By the way, @Nic Brough [Adaptavist] I've…

You may include that foo issue easily on your JQL search by adding: ...OR key = FOO-1

Workaround: As the omission of the field only occurs when there are no issues with a value in that field, why don't you add a foo issue with a value for that field, easily identifiable so that you can remove the line after the export?

I agree it would be a great feature for Site Administrators. However, provided that only Site Administrators can actually see the list of users who belong to a certain group, allowing normal users to add groups in mentions or watchers would create lots of undesired notifications, and other users would have genuine…

Note that one board can show issues from any number of projects.

There are also other alternative ways based on Security Levels, but that approach would require much more steps for achieving what you need.

The easiest way is creating a new project for that third party's issues, modifying the board's filter to include issues of the new project as well.

Yes, you can do so if you have the Bulk Change global permission. * Go to Issues > Search for issues to enter the issue navigator. * Enter your JQL search, ie: project = <project key or project name> * Perform a bulk change: bulk.jpg * Select all issues by clicking on the top-most checkbox. * Select Edit as the operation.…

I think JQL queries return issues, not users, and therefore there's no way of achieving what you need through JQL.

Will watchers receive the notification on issue creation? Normally, watchers of an issue can be added when the issue has already been created and, therefore, they do not receive a notification until the issue gets updated...

Then create a transition from Closed to Closed and name it ie: set redolution. Add a post function to it to set the resolution Done. Finally, perform a bulk transition isuues operation using the new 'set resolution' transition.

mmm... Try adding the Resolution field also to the View screen and let me know if that let's you fix the resolution. If that weren't letting you set the Resolution, I would think that your query retrieves issues from some other projects where the Resolution field has not been added to the screen.

Edited my last comment.

(Edited) Find your screens here: https://<YOURS>.atlassian.net/plugins/servlet/project-config/<KEY>/screens YOURS = the customer subdomain of your JIRA Cloud instance KEY = the project's key (ie: Human Resources project is likely to have a project key like HR, which precedes every issue: HR-1, HR-124, and so on) Click on…

Finally, do not forget to publish the workflow draft so that your changes are actually applied.

Likewise, in a similar manner, you should add a post-function for setting the resolution to None (clear the resolution field) on every transition that lets reopening the issue. That's all transitions that go from the Closed status to any other statuses, including global transitions (those that have the 'All' tag,…

Edit your workflow in the Diagram mode and click on the transition (arrow) that goes to Closed: post-functions.jpg