Nic Brough -Adaptavist- Expert

I guess you have used a number type of field for this field. These can't be used as grouping fields for the gadgets that group results, only list-type fields can be used. You will be able to get the numbers out in the gadgets that display fields.

"Already in use" is probably the more useful message. I do not think it is entirely clear here, but what I think may have happened is that * Your old system had itv.atlassian.net * You didn't use it (and/or pay for it) for a while, so Atlassian shut it down * Someone else requested the same url, and now has a system…

Have a read through https://confluence.atlassian.com/adminjiraserver/jira-applications-installation-requirements-938846826.html - it is aimed more at physical servers, but that's not hard to translate into virtual machine requirements.

One of the big weaknesses of the Khoros (nee Lithium) system is that it does not let us comment on questions, we have to use "answer" when we want to do anything. That, of course, includes clarification questions or comments that lead to a discussion. This particular question is absolutely one that I would never have…

You have a problem with your database - you will need to debug why it is saying the password has expired and fix that. When you are trying to "get to the log files", what are you actually doing? "error scan failed" is not an error message I would ever expect from logging into the server and opening the log in a text editor

Yes, you will need some. Start at https://confluence.atlassian.com/bitbucketserver/bitbucket-server-installation-guide-867338382.html

You will need to set up dummy accounts for each department, and then write some code that can amend all the fields.

See https://www.atlassian.com/licensing/jira-software The people named as primary and billing contacts in your account were all emailed several days before your subscription expired.

You will need to get on to a client machine that has access to the internet and can reach the Jira server too. You can then download the app as a .jar or .obr file from the marketplace, and use "manage apps -> upload an app" to install the plugin.

It's accepted because the answer (and/or its comments) are a good explanation of the current way things work, and why.

entities.xml and dbconfig.xml are very very different files. You should not even be looking at entities.xml here. The only file you need to think about during your "copy live to a staging machine" is the dbconfig.xml file in the Jira home directory and the changes in there should be just to point the service at your…

Ok. Any chance of context or a question?

No, because you are changing the rules on what is done and not done.

If you want to limit what people can see, you need to be able to identify them so you can apply the rules about what they can or can not see. That means having an account. You can give these people nothing other than "browse project" permission such that they can see issues but nothing else. But they'll need an account…

The error message has nothing to do with your script as far as I can see. Can you tell us where you are using the script? 

You have one or more lines in your csv where the summary or epic name are empty.

In which case, you do not have a real problem. 8.13 is an early access release, there's no support or suggestion that it will work at all. It's not working for you, so, um, write it off and don't waste any more time on it. If you need a working version, get one of the main releases. If you're just playing with it as a…

Look at the list of screens in admin. That tells you all the places a screen is used.

That is trying to get a list of tabs. It does not appear to have any security problems.

Go to your my.atlassian.com and re-subscribe to the service.

What do you mean by "detailed view"? What are you doing to get that?

No functionality or data changes when you "move". You just apply a licence that tells the software you have X users who can use it until the end date. 

Put it back on the screen(s) you removed it from and make sure it is not hidden in the field configurations for the project.

You should not edit those values, they are there for a reason, and editing them smacks of someone lying about what they were doing. Leave them alone. And exactly what @Joe Pitt said - you should never touch a Jira database (exception is when support tells you it's the only way to fix something)

Part of my job is to review business processes and tools. For a place using Jira for one purpose, 100 custom fields is the point at which I start to say "if you think you need these, you probably have a broken process".

Click on your profile icon at the top right. If your admins have allowed "create personal space", there will be an option to do it in there. If they have not, you will need to ask them to enable it.

Yes, we can sign up for it and use it. Could you explain where you are stuck?

Yes, they both work from a board filter, which selects a list of issues that the board draws in. If you use the same filter for both boards, and you set up the boards to understand backlog, in progress and done in the same way, then you'll get a consistent backlog (and the rest) across both of them. It is not uncommon to…

Jira does not yet work on MySQL 8. You'll need to move back to 5.7 to make it work See https://confluence.atlassian.com/adminjiraserver/supported-platforms-938846830.html and select for the version you are trying to install if it's not 8.11 that the doc currently lands on.

* Doctor Who (there's almost 800 surviving episodes...) * Star Trek * Firefly * Blake's 7 * Black Books SciFi nerd? Nooo, not me, honest.