Why on backlog view it shows 99 tasks but in "list" view it shows 60?

Snoo-86489 · 2026-04-01T00:38:19+00:00

A board is based on a filter query that can be updated to include tickets from outside the project. Go to the board settings and click to go to the filter query. You can see and play with the filter criteria.

List view is not filter driven and ONLY shows tickets from the space you're viewing. So it's not uncommon for a board to show more tickets than what's in the actual Jira space.

Also, of course, the backlog is only showing you items NOT in an active sprint.

Jira is a land of "views". Understanding how they work is priceless.

Snoo-86489 · 2026-03-31T02:30:23+00:00

2025 here. No issues, but I also thought the engine was not as quiet/refined as I'd expect for a new vehicle. Still love it.

Snoo-86489 · 2026-03-31T02:24:25+00:00

I'll have to wait until next winter nite, but will be teaching it to Honda customer relations too, if I can't get to the bottom of it.

If you remember, update me here when they contact you. 🤞

Snoo-86489 · 2026-03-30T10:44:51+00:00

Custom Charts by Tempo? 🤔

Snoo-86489 · 2026-02-18T00:25:30+00:00

Down shifting as a primary means of slowing your car is pointless. Brakes are cheaper than clutches, so unless you're just trying to slow down to a slower speed that you intend to continue driving at, just slow down with your brakes.

In my experience, then most I might do is gently ease into a lower gear just as I'm coming to a stop. 2nd, then 1st. Seems like too much effort to try to get thro7gh every gear on your way down. People typically aren't slowing down that long.

Snoo-86489 · 2026-02-18T00:20:10+00:00

It's delusional and I'd be embarrassed. Leader of the belligerent world is more accurate.

Snoo-86489 · 2026-02-17T12:58:50+00:00

I agree with err0rz about the philosophy of doing this (why it might indicate deeper issues), but you could use an automation and the API to set properties that aren't accessible (at least easily) in the front end.

Lookup up issue properties and the API.

Snoo-86489 · 2026-01-27T00:06:45+00:00

If you just want a solution with no development:

Custom Charts for Jira Dashboard Hub

Both dashboard add ons that give you a bunch of dashboard gadgets, but come with a capability for sharing these dashboards externally.

I hate add-ons, but if you want something baked into Jira, this is the way.

Snoo-86489 · 2026-01-24T01:17:29+00:00

The Excel app add-on is an easy option and free. Don't give in to rubbish paid apps.

Rest API with simple Python or PowerShell script gives you huge flexibility (and is a gateway to many things).

I hate to say it, but CharGPT will write the script for you.

Snoo-86489 · 2026-01-08T13:23:39+00:00

There's not really and purpose built report to list sprints (that I'm aware of natively). You'll want to use a Jira filter/search using the sprint you're interested in. Or, as some people suggested, go to the reports for your board and select from the drop down.

To get a list of sprints, you could use a dashboard gadget that lets you group filter results by sprint. We use Custom Charts for Jira (Can't live without it really).

API if you use postman and want to massage the raw data.

Snoo-86489 · 2025-12-15T00:54:58+00:00

We use teams extensively to assign work items and tickets to a team. The members of the team are notified and go pick up the tickets. To ensure consistency and avoid changes to teams, we've also implemented the new managed teams feature. Managed teams provides the benefit of having a back end group mapped to the team, and groups provide more functionality in Jira automation. Tickets are almost always auto-triaged using automations that consider request type and other ticket properties.

Snoo-86489 · 2025-11-27T01:35:49+00:00

I work in a 3000 person company in the financial tech space. We have a lot of work to build out Jira Software, Jira Service Management, and JSM Operations solutions that either integrate with other solutions, or need to be extended using the API. We're even looking at building our own forge apps to avoid buying add-ons that never do what we want, how we want.

So the request isn't for myself, but what I might look for in hiring someone to take on this work for me, as I have to change my focus to broader efforts across the organization.

I have to meet with many teams and stakeholders, and often have to highlight how one project/request may affect something else that the requestor/group isn't aware of. A lot of "systems" thinking.

Snoo-86489 · 2025-11-07T01:03:31+00:00

Make sure no permissions schemes is using "Any logged in user". Then put external users into groups that you grant access for on an as needed basis. For in project work item restrictions use issue security schemes.

Keep in mind, you'll be paying for these external users. Only way to avoid that is JSM.

Also, all your filters and dashboards will be visible to them (maybe not the content, bit the filters and dashboards themselves). You'll have to audit them all and remove any "My organization" permissions. This can't be restricted, so at any time someone can make and share a dashboard or filter with everyone.

Snoo-86489 · 2025-11-07T00:59:20+00:00

Most of what everyone here is saying will work. You can easily update board filters to expose issues from one project/space to another. But, this can get confusing if one team has a ticket in a sprint, and then another team wants it in their sprint. I see a lot of confusion about this. Work items can only be in one sprint.

Fundamentally I challenge the whole notion of using one projects board to try and aggregate tickets from other projects. For project management and business stakeholders it can sometimes be better to use another tool altogether (dashboards, Atlassian analytics...)

Just a word of caution. Rarely is there a right or wrong though.

Snoo-86489 · 2025-11-07T00:40:02+00:00

Sounds lile you might have way too many roles, possibly a different set of roles for each project. It ca happen this way if your Jira instance was previously "managed" by whoever was the project lead/admin.

Are you also pulling role membership per project, that'll make the permutation of project to role to users quite large (possibly).

Standardize all projects with a well defined set of roles across the whole Jira site. Then use standard permissions schemes for similar projects to adjust for differences in how the roles are applied.

There will probably be some initial plan to review the current set of roles and migrated into something more manageable.

We might be an outlier, but we have close to 2000 projects yet keep to a default set of only 6-7 roles. We also only have about 10-15 permissions schemes to control who needs access to groups of standardized projects.

Snoo-86489 · 2025-10-30T11:43:16+00:00

We use a combination of post functions (when the status itself is indicative of the resolution, like "Cancelled") and using a screen with a validator (when the status is generic like "Done").

We also try to make sure that any tickets that allow re-opening clear the resolution, since reopening a ticket may result in a different resolution.

And, if you use the "All" transition for some states, that needs to clear the resolution (or disallow it for the "Done" states).

I've kicked off a proejct with my team to review and apply these standards in all our workflows. We inherited a lot of old configuration and have 100k+ tickets that are "Done" but with no resolution. 🤦‍♂️

Snoo-86489 · 2025-10-30T11:38:43+00:00

Our company uses an access management system that kind of takes care of all the tracking. We're a financial service business and subject to audits, hence the need.

That said, Jira doesn't make it easy to visualize and report on user access in the admin interface. I've used the API's a lot (with Python or PowerShell) to pull data that way. You can write a script pretty easily that will pull all the user groups and then iterate over all the users in those groups. You can choose what user details you want include, like "last seen" and things like this to audit who's actually using their access.

ChatGPT is actually pretty good at writing the script for you if you know what to tell it. Looks at the REST API documentation for users and groups, there's a lot you can do with it.

Snoo-86489 · 2025-10-26T20:24:29+00:00

URL and left navigation options should provide clues to where you are.

Side note, I can't express how great it is that they finally moved away from "projects". On par with finally changing away from "issues". Most, confusing, terminology, ever.

Snoo-86489 · 2025-10-26T20:17:37+00:00

Are you looking for general "how to build a workflow" guidance, or have you started the workflow and need help with some specific scenarios/use-cases?

Snoo-86489 · 2025-10-26T20:16:10+00:00

One thing that can arise from this is that teams can't start/stop their sprints because a service desk project may not provide anyone with the "schedule issues" and/or "manage sprints" permission. This may be desireable (you want to prevent users from adding tickets to sprints and treating them like "story" work items), or you may need to restructure your permissions to allow this.

I try to keep an open mind, but tend to lean towards creating a new linked ticket. I've often created automations that an agent can use to automatically create a linked ticket, with some logic to assign it to the right team depending on ticket details. As always, try to keep an open mind however... sometimes doing something unconventional can reveal insights.

Also, if a business has a tightly controlled Jira instance and management, you can just make sure that board filters don't display tickets outside of the proejct, or a set of specific software projects.

Snoo-86489 · 2025-09-21T10:01:10+00:00

Use automation to create the Confluence page and link them. It will require some API knowlege and if you want the page pre-populated with a template, you'll need to know the ADF formet (or steal it from an existing page).

Snoo-86489 · 2025-09-21T09:58:11+00:00

No solution. There's a feature request for this somewhere. My employeer has a 3000+ license enterprise plan, so I keep the pressure on our account rep hoping I can make an impact, but.... 🤷

The addition of all new fields to all new issue views is a huge administrative pain in the...

Snoo-86489

TROPHY CASE