Nic Brough -Adaptavist- Expert

Welcome to the Atlassian Community! I think you may be in the wrong place. Could you explain what this has to do with an Atlassian product?

Are there any errors after this? These are now all warnings and information.

Ah, OK. I suspect you took your snapshot when Bitbucket was running, which often leaves it in a state where it looks like it is running, despite not being, so when you try to start it, it thinks it is already running. Have a run…

Take the resolution field off the screen, it should only ever go on transition screens. You set the resolution during the transition to closed, either by setting it during the transition screen, or by having it set by a post function (some boards let you set a simple tick box which does this for you)

We can tell it is Cloud because the poster does not have "priority schemes" under administration. Cloud only has one "scheme", every project has to have the same list of priorities, which is defined under the "priorities" you have mentioned.

Because it is possible to switch to basic if you've got a simple query defined. It would be poor UX to have a button that gets (apparently) randomly hidden and shown according to what the user is doing.

If you move issues from a JSM project to a development one, you lose the request and hence the communication with the client raising the requests. You should use development project templates, but don't move issues into them - train the agents to use "create related issue" when requests for development arrive.

You will need to give customers Jira Software or Core paid licences to enable them to create and work with issues, and you will lose the requests, portal functions, SLAs and so on that JSM provides.

Basic searches do not support "search for everything". Try adding a simple query to it (like "Project = ABC") and you should be able to switch to basic.

Yes it is, as I said before.

Welcome to the Atlassian Community! Make sure all your "done" status (for both issues and sub-tasks) are in the last column on the board)

Not with the validator you are using, you'll need to find or write something that can work with labels.

I am afraid that there is nothing you can do really. On server, you could unlock one of the fields and then rename or delete it, but that could break the functions that rely on it.

That log looks like you have not upgraded Bitbucket. It's still referring to the old version.

Welcome to the Atlassian Community! You should never assign an issue to many people, in real life, it will break things, you'll miss stuff. It's a terrible thing to do with an issue. But that from is the definition of assignee in Jira - the assignee is the person who is currently supposed to be getting the issue dealt with…

Great, thank you for clarifying that for me. So the next question is what is the rest of the startup errors you are getting? I mean, what do you get when you try to visit the server's site? And what are the other errors in the logs?

Labels are not simple strings, they're effectively handled as options - that is the data in the database for them is not a string, but an identifier for an object that has a display/search name (the label the users have entered). The regex validator is looking at the object, not the name of it when you apply it to labels.…

You can't do it directly, you will need to have the links in the email take them to another web server, one that is accessible without VPN, with a service running on it that can take the click, work out what needs to be done in Jira, and then connect to Jira to do it for the user, anonymously.

JWM projects are shown as "business" projects in the creation screens and the project list. Software projects get the more configurable Scrum and Kanban boards, but you don't actually need to move to a Software project to get a board that supports swimlanes. You just won't see the board in the project links if you do this:…

You give us two versions in there - do you mean you had 6.5.1 and upgraded to 7.21.5? Of Bitbucket? Or something else?

This depends entirely on what the new field is for - might there be a time when the other projects start to use it? You will need a different field configuration, or screens, or field context. Of these, the field context is the only one that might have a small performance gain - global fields slow the use of the index more…

The problem is your choice of "current issue" in the sub-task settings. There is no current issue in a scheduled task, you need to tell the automation which issue you want to create the sub-task(s) in.

Yes, you won't see any difference.

Inline edit is a global setting, on or off (for all fields)

Actually, it's the same on both. The *s only appear for fields marked mandatory in the field configuration, they won't appear for fields only made mandatory by validators.

What errors do you get when "the old server licence for 2000 people does not work"? Have you upgraded Jira to a version released later than the expiry of that?

Ok, then the other thing is that it is a Jira Work Management project, whos built-in boards do not have swimlanes.

Assuming the ***** are the same, then you are looking at the same page, there is no "sub page"

Could you explain what you are trying to achieve here? Not describe what you think is the way to do it?

Welcome to the Atlassian Community! You would need to set up something that can receive the click on the button on the email, and post it into Jira (as someone who can log into Jira)