Ignacio Pulgar Expert

In your JIRA Server instance, perform the following steps: * Go to the issue navigator and execute the following JQL for finding all issues with links to your previous JIRA Cloud:text ~ "https://<YOURS>.atlassian.net" * Modify the columns shown to be: Issue Key, Summary, Description and Accept Criteria. * Export the…

Alternatively, you may create a filter like the board's filter, but adding: ...AND status in ("To Do", "Pending") ORDER BY Rank ASC changing the statuses to the ones mapped to the backlog. After that, create a daily subscription to that filter for every user that should be aware of those issues in the backlog.

JIRA Cloud or Server? If Server, what version? This sounds as something worth opening a ticket with Atlassian Support: https://support.atlassian.com

Review who's the board's filter shared with. Maybe it was shared with a project role that no longer exists.

Your custom field approach is correct. The reason why the SLA metrics cannot be exported is here: https://jira.atlassian.com/browse/JRASERVER-62457 Regards

May you manually change the URL to get to the Shared Filters page? <JIRA Base URL>/secure/admin/filters/ViewSharedFilters.jspa

I've read the UI has changed on Cloud. May you click on Search and type Shared Filters?

Cog > System > System Info Although it will probably also appear at the very bottom of every page.

If the URL of your instance is <something>.atlassian.net, then you're on Cloud.

Are you on Cloud? Or what Server version?

Only JIRA administrators can change filter ownership. Regards

The order of issues is stored in an alphanumeric field named Rank, which behaves like a number. You may save some JQL filters using Rank, and subscribe to them in order to be notified of certain rank changes. However, this system relies on hardcoding known values into your filter, so it is not a handy method at all. If you…

YW! Yeah, it is difficult to find. As changing ownership is something you hardly ever do, I usually have to look for it in the docs everytime I need to do it. Maybe Atlassian could change its location to the same place where you can Copy a dashboard.

Hi Jack, Yes, you can: https://confluence.atlassian.com/adminjiracloud/managing-shared-dashboards-818578902.html Look for the section "Change the ownership of a shared dashboard". Regards

Natively, you have this JQL: status changed from x to y on <date> by <username> AND assignee was <username> on <date> However, such a JQL relies on you providing the assignee and dates, which is not very handy for reporting. assignee in membersOf("<group name>") would retrieve the correct issues that matched the condition,…

You will need an addon for that purpose. The cheapest one I know is Time Reports: https://marketplace.atlassian.com/plugins/timereports/cloud/overview Its Support is quite good and fast as well. Alternatively, I'd use eazyBI. It is more expensive than Time Reports, but can help you to create many other kinds of reports. It…

JIRA doesn't support that natively, but you can use a plugin like Script Runner, which has a convenient JQL function: https://scriptrunner.adaptavist.com/latest/jira/jql-functions.html#_lastcomment

Burndown charts consume story points once an issue is transitioned to one of the statuses mapped to the last (most right) column. Those charts cannot be set to consume story points based on any other events. However, you can map as many statuses as you want to the last column instead.

You may click on the cog icon > Configure in order to check the selectable options in each of those custom fields. If the options were the same for all of them, I'd say that you may delete all but one of them. However, as all those fields are displayed simultaneously in the same window, it is weird that users hadn't…

You're right on that point. I guess the reason why you might be interested in receiving just one daily email with the last updates is that you don't want your work to be constantly interrupted by so many notification emails. If that's the case, I'd go for a solution at the inbox level. For instance, Gmail lets you save…

Alternativamente, puedes descargar el codigo html de la página y buscar el número del custom field en ese archivo. En la misma línea que contenga ese número, encontrarás también el nombre del campo que buscas.

Si mal no recuerdo, una manera de averiguarlo consiste en: * entrar en la página de configuración de Custom Fields, en la que se listan todos los campos. * Pulsar la tecla F12 para mostrar la consola del navegador y hacer click en la pestaña Elements. * Hacer click en la opción para expandir todos los elementos, y después…

Note that mentions use the username, and not the displayed full name. Check your username in User Management or in your profile.

Try this JQL: text ~ "<username>" If that sentence works, you may add the remaining conditions from a specific board's filter.

What do you mean with tagged? Being the assignee of the issue? Being mentioned in the issue?

You may create a filter like: updated >= startOfDay(-1) And subscribe to it on a daily basis. As a result, you will receive one daily email with a list of all issues that have been somehow updated since the day before.

Indeed. My first thougt was about javascript being added to the announcement banner...

That behaviour seems to be a bug. You may open a ticket with Atlassian Support: https://support.atlassian.com

The easiest way to achieve that would be editing the project notification scheme in order to add the project role Service Desk Agents to the Issue Created event.

Provided that Done is the final status in that workflow, I'd say the most likely cause is that said status has the property jira.issue.editable=false in order to prevent already closed issues from being edited, which also affects transitioning capability. Should you want to get rid off of that property, you may: * Edit the…