Nic Brough -Adaptavist- Expert

The systems work from the information you give them about the users according to the licencing rules Atlassian have decided on. The problem is your usage of SQL that does not fully understand the logic of provisioning the users. I'd strongly recommend not using SQL, as it's giving you incorrect information.

No. Global permissions are the first layer of access control, space permissions the second, restrictions the third. Imagine Confluence without the restrictions function - you have to do permissions to tell it who to let into the space. Restrictions are done by page, later in the process of working out "who can see this"…

I'm afraid we'll need to see the logs to get any further with this one.

Click the pencil icon, click the licence box, delete the text, save. Watch all the functions disappear.

Why do you think you need to know? The .jar file is part of a package that you have chosen to install, as are thousands of other files. Rather than try to dive into why it is there as part of a (let's face it, very complex) piece of software you want to use, take a step back. Why are you asking? What are you trying to…

A licence is supposed to be allocated for each individual person who uses the system. You could do something like this with shared accounts, but, don't. You'll mess up your tracking. But you can still do it. It's a faff for your Jira admins, but possible. Imagine we have Alice, Bob and Charlie and they do support a week at…

Boards are a view of Jira issues based on their status. There's no way to change that, it's not what boards are for. There are a couple of apps in the marketplace that provide functions like that, but they're not called "boards", to avoid confusing them with Agile boards. Canvas is one word that might be worth searching…

The problem here is that you are using SQL to do the counting, and your SQL is incorrect, it is missing something. You can't match the licence count in the UI because your SQL is not looking at the right things. Does it take into account all directories in use, disabled users, and all the groups with all three possible…

No, it is not block-transactional. It is individually transactional - each post you make either works and updates the data, or it fails and makes no change. Each individual post. There's no way to roll back if a series of separate transactions fails in the middle - they're all separate transactions.

Nope. You've not actually attached or posted any screenshots. You've posted a link to images on systems we can't see.

And your point is?

There are no screenshots attached. Could you give us the plain text of the errors?

That's nothing to do with what you asked. That's about group management, not permissions.

Go to Admin -> Issues -> Issue types and select or upload a different icon for one of them. (It's one of the first things I do on a new Jira, I totally agree that the icons are far too similar)

Because the structure of a space is flat, and you need, and should have, unique names for objects within it. Oh, and Atlassian have worked with places where you ask things like "show me the definitive page about penguins" and the response is * Penguin * Penguin * Penguin Which one of those three is the definitive one?

I strongly recommend using SQL as the reporting tool of last resort. You'll need to build and maintain your own data dictionary, and believe me, you'll be in hell for a long time if you do that, and you'll then need to re-analyse on every new version of any part of the system you upgrade. Jira uses a database as a data…

One of your admins has removed the version report from the help text. There's no way to directly establish what version it is if they have done that to you. You might have some luck with a REST call though - if you ask for system info, it should usually return the version. See…

Linux isn't one OS, it's just the kernel of thousands of operating systems. It's not unusual for a corporation to support only the OSs it sells well on, and most Atlassian servers are on Linux-based OSs. I suspect if we asked, we'd get numbers at 80% if not higher.

I think you might be in the wrong place? Are you really using Jira as an appointment tracking system? Could you have a look at the "help" button? (Near the bottom left of the screen or near the top right - should be a question mark). Does it have an "About Jira" option?

No, sorry, I don't doubt you, I was fishing for more info in a really badly phrased way. Your screenshot is great, tells me that that issue should probably not be there. However, there's something not appearing on the wider view that I would expect and it might be the problem. Could you open up the full issue view and have…

I understand, I usually don't know how experienced someone might be so I try to write guides in simple English rather than Atlassian-speak. In the screen you are in, where I've said "result" is (sort of) the "Template" field. That contains the words you want to come out of a macro, but also the result of any code you've…

Some more questions though, as this one has got me curious... Are your behaviours for 1 and 3 on your list identical? Simply no screen appears at all? Not even a flicker of something on 3? In 2, you get a screen with fields, but does it also have comments? Can your user comment on the issue from the main view before the…

I would do 5.7 -> 6.4 -> 7.0 -> 7.target. And test 5.7 -> 6.4 a lot - if you have any problems, do 5.7 -> 6.0 -> 6.4 The reason for this is that there are a whole batch of gotcha's along that path that are removed by taking smaller steps. Do NOT skip 6.something -> 7.0. 7.0 has code in it that upgrades certain data items…

There are a few scripts in the library you might want to have a look at (as in "copy them") - see https://library.adaptavist.com/search?page=1&products=jira&term=create

No, I'm afraid the validators in Jira off-the-shelf are very limited. But there are loads of apps that provide validators in the marketplace and some are free

The point of a backlog is listing, ranking and selecting the issues are supposed to be able to go across the board. If an issue can't go across the board because it's not on it, there's no point having it in the backlog.

As a consultant, it's my job to explain why things don't do what people expect them to. It is often that they have not grasped something, rather than a flaw in the software. Jira Software tries to support Scrum at its most simple and plain usage. If you are using estimates on sub-tasks, then you're probably not using it to…

You would need to make the Jira project(s) anonymously accessible, so that they can see the Jira issues.

There are only two things you'll notice if you de-activate a user: * The de-activated user will not be able to log in * The de-activated user will no longer appear in most user selection fields as an option when creating/editing/assigning/etc. (They will remain in place when they're already selected in the fields, and…

There is a condition on the transition from dev-complete to released that is blocking you from progress. Talk to your admins to find out what it is.