Ignacio Pulgar Expert

Oh, I'm afraid that's not doable natively. You would need to use a plugin like ScriptRunner for that, which counts with measures for checking issues meeting certain conditions for their escalation.

You may check the access log. Maybe: * The user accidentally clicked the 'Assign to me' link. * An automation rule (service desk) was fired to set the current user as the assignee when certain conditions are met. * A workflow post-function was fired by the user by transitioning the issue, indirectly assigning the issue to…

Try your quick filter after setting your board simlanes to "no swimlanes".

If your board's swimlanes are based on Stories and you apply a filter that excludes subtasks (like type=Story) then the swimlanes will have no subtasks to show, and therefore, nothing will be shown in that board.

If you don't want to use the backlog, unmap all statuses from the Backlog column. In that case, you will likely want to map those statuses to a column of your kanban board.

Go to your board configuration > Columns and map at least one workflow status to the Backlog column. Ensure all workflow statuses are mapped to a column in order to prevent issues from disappearing on reaching an unmapped status.

Add the field Time Tracking to the Create and Edit screens, so that you can set an Original Estimate on issue creation/edition.

You cannot leave one of the two link names blank. In some cases, it is correct to use the same name for both (ie: relates to), but more frequently they will be different, one of them with a verb using the third person of present tense (ie: causes) and the other one with the same verb in passive form (ie: is caused by).

Hola Alejandra, Lo primero, comentar que en este foro tendrás muchas más probabilidades de respuesta si tu pregunta está en inglés. ¿Puedes añadir un par de capturas de pantalla: una de un test clonado bien y otra de otro clonado mal? Cuando hablas de pasos, ¿te refieres a los de lis workflows? Añade más información…

Date comparisons can just be performed with the help of a plugin, like ScriptRunner.

Thanks!

Awesome! Would you mind accepting my answer?

What's the full stack trace of the error being thrown? You'll find it in atlassian-jira.log

May you try this slightly different JQL?: ... AND (resolution is EMPTY OR resolved >= -7d) ...

If a document has been added to an issue as an attachment, then every user with enough permissions to see the issue will also be able to see its attachments. So, you can either control who can view the issue, or add a link to the confidential document allocated in an external tool from which you can control who to share…

Just Tested is unchecked: Project = CORE AND status = "Awaiting Acceptance" AND Review = "Design Reviewed" AND Review = "Code Reviewed" AND Review = "Needs Review" AND Review != Tested

I think so, but I'm not 100% sure on this one. I'd suggest performing some tests in a dummy project and board to see the results. Btw, thanks for accepting my answer. Regards

Hi Manohar, Sprint Reports will not be recalculated, as they should keep the values they had when they were created. No workaround for this. However, future Sprint Reports will be created according to your new setting, being estimated on Story Points. Glad to hear the trick worked. Would you mind accepting my answer?…

You may save a filter like: type=bug and priority>=major order by created

Hi Shawn, Maybe you can: * Save a filter like: type = subtask and sprint = sprintName * Add a Pie Chart to a dashboard, and set it to use that filter, and set it to be based on Status field. It might not be exactly what you need, but it would help getting the right numbers. Regards.

The easiest way I can think of is: * Go to the Issue Navigator and type a JQL query like: "Story Points 2" > 0 * Ensure the only columns being shown are Issue Key and Story Points 2, and then export the results to 'CSV (current fields)'. * Go to the CSV importer and select the csv file you've just downloaded for the issue…

Hi Michael, The list contains just users who have permission to view the issue where the @mention is being included. So, the list of suggested users can be limited by removing the Browse Projects permission from those users who are not involved in that project. Regards.

Hi Kelly, The subtasks need to be converted to tasks first. To do so, enter the subtask's detailed view, and then click on More > Convert to issue. Depending on the JIRA version, it might be displayed an ellypsis [...] button instead of the More button. Once all subtasks had been converted into tasks, enter the task that…

The board is probably set to base its Swimlanes on Stories. Change the Swimlanes to not be based on Stories in order to make your subtasks viewable in the board.

Hi Eitan, You may prevent users from logging time in Epics by following these steps: * Set Epics to use a different workflow in your project(s). You may need to create a new workflow. A workflow with just To Do, In Progress and Done statuses would be more than enough for Epics. * Edit the workflow, click on the status To…

If the field is set to use the Wiki Style Renderer, it will include the options for adding attachments and so on. Regarding size, just ensure you do not select a single line text field type. Please, try it, as I'm quite sure it will meet all those requirements. Regards

You may create a custom text field, ie. named 'Technical Solution', which could be used to contain the info you wouldn't like to be spread over the full conversation with the reporter.

Column names are mapped to workflow statuses in the same place where you took your screenshot from. The first thing you need to do is ensuring the worlflow you set in the project/s uses the statuses you would like to map to each of those board columns. Once you have a workflow with the desired statuses, they will be…

In JIRA, each issue must belong to exactly one project. It's not possible for an issue to not belong to a project, nor to belong to more than one project. Mind that the issue key is formed by the project key plus a number.

Depending on your needs, you may prefer to disable notifications and create filter subscriptions instead, but it is generally better to receive standard notifications.