Ignacio Pulgar Expert

JQLs work like a WHERE clause added on a SQL starting by "SELECT * FROM issues_table WHERE ... <JQL>". So, a JQL will always retrieve just a list of issues that matches the specified conditions. Therefore, not being able to query the table of historical status changes directly, you will not be able to obtain its last…

You can effectively achieve that by taking the screenshot from an account with access to the project (Browse Projects permission) that doesn't belong to the group or project role to which the comment was so restricted.

For measuring what, exactly?

It works like a charm. Thank you!

Can you reword your question? I do not understand...

Are they Service Desk Customers, with access restricted to the Customer Portal?

You might want to have a look at this addon: https://marketplace.atlassian.com/plugins/com.thed.zephyr.je/cloud/overview

The URL to Redmine importer is: https://<YOURS>.atlassian.net/secure/admin/RedmineSetupPage!default.jspa?externalSystem=com.atlassian.jira.plugins.jira-importers-redmine-plugin:redmineTrackerImporter

Hi Nic. I confirm that Redmine is also available on Cloud for importing issues: https://<YOURS>.atlassian.net/secure/admin/ExternalImport1.jspa Cheers

Thank you for your answer.

I think I've found the answer I needed: "Email notifications will only be sent to people who have permission to view the relevant issue — that is, people who: - have the Browse Projects project permission for the project to which the issue belongs; and - are members of any Issue security levels that have been applied to…

You should direct your request to Atlassian Support.

Sorry, I don't know how to help you, but I'm interested in how to create a similar utility that uses API calls. Could you guide me on how to build such an utility from scratch? Thanks.

I can't help you but for suggesting you to edit the title of your question to a descriptive one, so that you improve your chances of getting the answer you need. ie: Test cases not getting reflected on Cloud.

There are kind-of built-in ways to achieve it. You may save your query as a filter, ie. with name 'Epics' with this jql: type = Epic After that, you can use your saved filter in other queries like this: resolution is EMPTY and filter in (Epics) You can use either the filter name or the filter id, minding that using the…

JQL is useful for retrieving issues that match certain conditions. JQL cannot get anything else than issues, and all you will be able to display is their fields. The date a story went into a status is displayed in the issue detail view, into the History tab. While the issue's history of changes cannot be displayed in a…

Have a look at this: bulk csv import

Exactly. Just wanted to point out some specific built-in ways of grouping issues.

What Nic has said is true: there's no way of using a GROUP BY clause in JQL. Nevertheless, you have several built-in ways of viewing issues grouped by a specific field through the inclusion of gadgets on a dashboard. Have a look at these gadgets: * Issue Statistics * Workload Pie Chart The results shown are clickable so…

It's likely that the project names which start with the same sequence of characters are actually sub-parts of the same project/company. If that's the case, you might consider merging all those similar names in just one project, and create one Component for each of those separated projects.

It is likely that entering one (or more) of those the green statuses (statusCategory = Done) a resolution is set, either manually or automatically. JIRA considers issues as open if they lack a resolution value, and as closed if they have a resolution set. With that consideration in mind, many of the built-in gadgets and…

Cannot be done without help of a plugin. For JIRA Server, you can probably have SLA functionality on a non-Service-Desk project through the use of a plugin (ie: SLAdiator, Time to SLA and Days Elapsed Plugin). Maybe ScriptRunner for JIRA enables a workaround based on the Due Date or any other Date Custom Field. For JIRA…

* Go to the board. * click on Board button (top-right corner) and then Configure * click Columns option * drag&drop the desired column to the position you want

I would suggest another approach: * Create a screen with your custom field and possibly the Resolution field too, both as required fields. * Add your screen to the transition(s) that go to the status Done ('Adding a transition', point 5, second bullet). * Publish the draft of your workflow. After that, your screen will be…

Edit the workflow and click on the transition that go to the status Done. On the menu on the right side, click Screen, and select Resolve issue screen. From that moment on, changing the status to Done will prompt a dialog window to enter the Resolution.

You can create a custom text field in JIRA named 'Remark', add your remarks there, and it will be displayed by the Confluence macro. If you think I've answered your question correctly, consider accepting my original response with this thread of comments Regards

You can probably get what you need from the Edit page: macro.jpg After that: configuration.jpg In the display options, select Table and fill in the columns (fields) you need to be shown. You can show information from just one issue by using the following sample JQL: key = KEY-23 where KEY-23 needs to be substituted by the…

I don't think it is possible to add any extra issue fields on Confluence Cloud. Even Confluence Server needs an addon for achieving that: https://marketplace.atlassian.com/plugins/com.atsistemas.jira.plugins.pageme/server/overview But, unfortunately, it is not available for Cloud.

???

You are right, that kind of messages suck.