Ignacio Pulgar Expert

Hi John, Bold text is the current way in which Service Desk marks the currently selected queue. So, I'd suggest using the special character '└ ' (Alt + 192 followed by a whitespace) as a prefix for those sub views, in example:

For doing so in Active Sprints, follow these steps: * Go to Board > Configure > Swimlanes * Base swimlanes on Queries * Set one JQL query for each priority (ie: 'priority = Blocker')

Go to Board > Configure > Columns and map the Blocked status to a column (other than the most right column) by drag & dropping it. In case of doubt, you may post here a screenshot of your board's Columns configuration settings so that we can help you further. Regards

Unfortunately, if Dashboard Utilities plugin is installed in unsupported JIRA versions, errors are expected to be thrown. I will create an article soon to properly explain the available workaround for creating a dashboard configured in such a way that it could be used by your 50 projects, each with the data that are…

Maybe it is one of those new kanban boards, with backlog as a new feature, instead of a scrum board?

May you ensure the property key doesn't have any leading or trailing whitespaces?

Story points are automatically shown in the backlog as soon as you set a value in the story being shown:

The backlog won't show issues which are in statuses that are either: * not mapped to any columns * or mapped to the most-right column

I've tried it like this and it works like a charm:

A few lines below that you should find the "Filter Query", which is what we need.

Of course, I'm assuming you know JIRA's built-in 'Copy Dashboard' option, and that you need each of those 50 dashboard to show different data. By the way, if that's the case, there's also a workaround for making the very same dashboard capable of showing different data dynamically, which wouldn't require a plugin, but just…

That's doable just with the help of a plugin. Dashboard Utilities looks to be a promising one for your needs, as it provides you with Clone Dashboard capability. While ScriptRunner counts with a built-in script to copy a dashboard from another project, it can do so just on project creation and requires the underlying…

What's the board's filter? Do you have any active quick filters applied to the board?

Is your user account included into the project role 'Service Desk Customers'? If so, try removing you from that role and test again.

Have you tried removing the ORDER BY clause?

I think the issue can be fixed by changing your UI display language to English from your user profile > preferences. Anyway, I agree it is a bug, and have already voted for it to be fixed.

Nope, being that the case, labelling the issues you need to keep track of is the best approach :)

The method you're using is OK. Note that the Sprint Report will show scope changes, so adding a bug to an already started sprint will be noticeable. If you have ScriptRunner, then you can use this JQL function, which would remove the need for labelling issues added to a sprint after its start:…

Check this similar question, which describes the problem: https://community.atlassian.com/t5/Jira-questions/How-does-a-query-JQL-look-for-non-integers-in-the-JIRA/qaq-p/637951 There's a feature request for solving this problem: https://jira.atlassian.com/browse/JRASERVER-45545

Check that: * You have Create Issues permission in the project the issue belings to, * There are no workflow properties which prevent you from cloning the issue.

Yes, you are using mail handlers for their intended purpose. It's true that it is really easy to configure email requests in Service Desk projects, but you cannot benefit from that feature without adopting a very specific way of interaction with your customers. People in charge of communication with customers would be the…

Nothing in particular, as you can always rebuild the index from scratch by selecting a full reindex, instead of the option to do it in tge background.

That's only doable by using a plugin. Here you have how to do it with the help of JIRA Suite Utilities (JSU) addon: https://community.atlassian.com/t5/Jira-Software-questions/How-to-set-current-user-in-custom-field-in-my-WorkFlow-Post/qaq-p/389110 It requires: * Creating a custom field for storing the username * Set a…

A few months ago, we experienced having to restart JIRA every 4 days because a third party plugin was leaving too many files open. We fixed it by upgrading the addon to a higher version which fixed it. May you post here the list of user-installed addons?

Just for your information, those users from addons do not consume any licenses, nor count to your app user limits.

I've just tested this on Cloud: So, you may: * save a filter like: assignee in membersOf("inactive-users") * add a Pie Chart gadget to a dashboard based on the assignee field, set to use the filter created in the previous step. The pie chart will show the list of assignees in the group inactive-users, (checked it works…

The indexing language is relevant for how Lucene stores words and special characters, which is the technology that powers text searches in JIRA. Why would you need to prevent users from displaying the User Interface in the language they want? I don't think it would save a significant amount of resources, and it's a nice…

As an alternative to using Issue Security Levels, you may create one scrum board for each of those groups of users. Each board should: * be shared just with that group of users, * have a filter with the appropriate combination of labels an components to filter out the issues that are not of their interest. Note that this…

Ordering by Rank ASC is a requirement for the drag&drop to work; no workarounds for that. The best you can do is reordering them manually, possibly by taking advantage of multiple selection capability > mouse right click > send to top/bottom.

You can potentially do it by applying this property to all workflow steps used by the project: jira.permission.create.clone.denied Ensure the workflows in which you add this property are not used by any other projects; otherwise the clonation would be forbidden in other projects too.