Nic Brough -Adaptavist- Expert

I'm afraid the only way to do this is to read the permission schemes and user setups for every project, one at a time.

Fields in Jira are (rightly) suposed to be telling the viewers the same message. having different views based on who someone is, essentially is a "lie". People need to see data and form their own opinions, not to be lied to. Tell everyone the same thing, be honest and open, and let people work from good info.

I do not understand "next to done as closed". If it is not done, it is not done. Could you explain how "it's not done but it is done?" To simplify - is it done, or is it it not?

So, I hate "necroposts", where people comment on something that's really really out of date. So, my first - have a look at "Jira Align". It implements SAFe

NO. Absolutely no. The last column in any (allegedly) Agile board is done. All the other columns are not. The last column is "done" Everything else needs more work, so it is either in backlog, to-do, or in-progress, depending on your more detailed view. What matters is "done". Done in Agile means "no-one might need to do…

Behaviours was second on the list of things to add to "ScriptRunner for Jira Cloud" for a very long time for the SR team. First were Conditions and Validators, but Atlassian finally gave us a way to do them. There are no ways to do Behaviours, Atlassian Cloud simply can't support them, yet. But please, do reach out to…

JQL is not SQL. JQL only finds issues, it has nothing to say about the content of them (except for the order, which some reports use) For your reporting, first find a report that can group issues together, and then configure it to look at "status category"

Jira (and most of the rest of the Atlassian software suite) are server/client, not local. To edit them, you need to connect your machine to their service. That said, there is a rather decent Jira desktop client which does a "sync" if you're offline -…

"Done" items should never appear in a backlog, and if you have your board set up correctly, you won't have them there. Your "done" items should be in a status that is in the last column on your board. Start there and check the issues that are in your backlog for their status being correct.

I'm not sure what the "validate" means in this question, but I am 100% with you on "get in SPCs and talk to them about how you would want to work"

Actually, the answer is "no". You can only have one simplified workflow which applies across the entire board. If you de-simplify, then yes, you can use multiple workflows that say "simplified", but they are not simplified any more, they're just standard workflows with "simplified" in their name.

You do not "move issues into a filter". A filter is a list of issues that match a search. If you say "balloons = red" in your filter, then you'll get all the red ballons. To make issues "move into a filter", edit them so that the filter selects them. In my example, colour all your balloons red.

If you log in as an admin and go to Admin -> General Settings -> Advanced, then look for the property jira.table.cols.subtasks, you will find you can add columns to the sub-task display. Be warned * It may do odd things if you add a custom field to it and later delete the field (although absolutely nothing damaging -…

You have almost answered your own question: > I have 10 isssues for project. [...] 1st query matches to 7 results. 2nd query matches to 5 but only 3 are displayed. No more displayed This is correct - 7+5 is not 10. Jira makes the assumption that the swimlane at the top is the most important to you, and then each one below…

Remote applications should generally use the REST API to talk to Jira. See https://developer.atlassian.com/server/jira/platform/rest-apis/ as a starting point.

If this is via ScriptRunner, you can enter just cfValue("name of field") > 1

I would reach for issue level security 

Pick an issue that went back into the backlog. Check the resolution of the issue, then the status. After noting the status of the issue, go back to the board and check that that status is in the very last column on the board.

Could you explain what this has to do with Confluence?

It's the same as before - you'll need an app to provide more comments-like fields.

You have to look at all the sub-tasks on the issues listed, making sure they are all in the last column on the board.

What do you mean by "filter wave1"?

Could you show us a screenshot? That does not happen to me.

So all you're doing so far is generating a simple url for opening a browser on to a Jira issue. You will need your QR software to generate a REST call to update the issue, then take your system to it.

You may need to explain what you mean by CSP (Corrugated Steel Pipe?). I am guessing that you're trying to stand up a new Jira server and transfer your existing system into it. You can either move the old server on to the new one wholesale, as that will keep the settings, or regenerate a new licence by changing the server…

You'll need your 3cx software to connect to Jira over the REST API. Atlassian support the REST API in full, so it's over to your software to work with it. Jira Service Desk is assumed because that is what the original poster said it was about - see the labels towards the top right of the question.

It happens because your account does not have permission to use that transition. Check the conditions on the transition to see what the rules are for who is allowed to do it. Most common is a condition for "only people in Role or group", but you'll also want to check that your account has the permission "transition issues".

I;m afraid that next-gen projects do not allow most of the things we need yet, including the change of ownership

Just "Epic" - do not rename those. Stories and the rest, fine.

Confluence works way beyond your old and tired ideas of Sharepoint (where documents go to die), Slow Toss Notes and the rest. It is, at heart, still a wiki It's content is as liquid as you suggest it should be, in my experience. I suggest that you get over the old document concept, focus on information and adopt the use of…