Nic Brough -Adaptavist- Expert

You'll need to create a new Company-managed project and move the issues into it. Advanced Roadmaps was originally written for Server, before team-managed projects existed. TMPs are very different in shape to CMPs, and AR simply can't yet work with them - TMPs don't share fields for example, and that means AR can't work…

Have you tried reporting it as a bug to them? Last time it was, three years ago, it turned out to be a fault in the browser.

Cloud does not yet support the ability to write Behaviours for Cloud, so you can't do it at the moment.

This sounds like you have used Scriptrunner's Behaviours on Server in the past. Cloud does not yet support the ability to write Behaviours for Cloud, so you can't do it at the moment.

Cloud does not have the option to turn off emojis.

The two fields work differently. Tempo doesn't get to tell Atlassian how to implement fields in their Advanced Roadmaps, and Atlassian doesn't tell Tempo what to do in their apps. I do understand they are talking to each other about it, with the move to be dropping Tempo Teams and Tempo using the Atlassian one instead, but…

I think "contains" is misleading in the name of the function, it's more "like" than "contains". The English version of your query is closer to "and there is a label like 'ServiceNow'" But the answer is a simple "no". ~ searches for text in text fields. Labels are a set of fixed terms, a select list rather than text.

I think you can pretty much copy and paste the script over at https://library.adaptavist.com/entity/remove-specified-users-from-a-group - swapping the line at the end from removeUserFromGroup to addUserToGroup

Yep, there's patterns there, but that is now telling us it's some people on Chrome on Ubuntu. And what is the difference between those of us who do not get the problem and those that do. 90% of my browsing is from a Ubuntu-based machine, and 95% of it on Chrome. I have never seen this. Until you can do that, there's pretty…

This is usually caused by the unix user you are logging in as not having a valid shell. or ssh settings. The "can't open /dev/tty" bit near the end is the giveaway. Try logging in manually, you will probably get the same error. If you do, then you will need to log in as another user (one who can use su or sudo to change…

I'm trying to avoid the obvious ones (money, beer, pizza, time, kittens, etc) and go for the general "new games and puzzles". From Bridge through to Gloomhaven, crosswords to wordle, jigsaws to Lego etc.

You could use an "all status can go to this status" transition, but the "tree" you are seeing in your last screenshot is done by re-using a transition. If you go to a status and add a transition to it, the pop-up box offers you a "reuse transition" option, which lists exiisting transitions that can be reused.

It's in the jira data directory (jira home), it looks to me like you are looking in the application installation directory, which is separate to the data. You may also find that there is not one. Most installers don't create one any more (older servers used to create one with a comment about the file being deliberately…

You can limit the lists of reporter and assignee with the project permissions. Only people with "create issue" permission will appear in the reporter list, and only people who have "can be assigned issues" permission can be assignees.

> closed issues which are not on any board If they're not on the board, it can't know whether they are closed or not, because they are not in the last column.

How to get rid of what? You have not described any problem or error here?

Again, could you read the application log, as I asked in the original answer?

That's the wrong way to approach "user not knowing what they are doing". The explanation you want to give them is content, not links jammed into navigation.

Status don't duplicate, they don't belong individually to workflows, they are selected by a workflow from the global list. You might have "in progress" used in workflows X, Y and Z, but there is only one status there. Could you show us how "it appears to me that there are 2 or more times to the selection"?

Ok, so what do you get in response?

Welcome to the Atlassian Community! Jira fields are independent of each other, there's no function for having other fields connected to any of them.

There is no way to remove this custom field, it's necessary for the functioning of some of the advanced apps. You'll need to either migrate your existing field over into it, or rename your existing field to something to distinguish it from Team.

I'm not sure what you are looking for here. "And: create a new sub-task in project system access management" seems perfectly clear to me.

You'll need to explore other project migration routes. These would include * Lossy transfer (set up the project manually, export issues to CSV and import them) * Going via a dev system (clone your 8.13 system to a dev system, upgrade it to 8.20, then use project import) * Apps that are built to transfer config and issues,…

Welcome to the Atlassian Community! Could you explain what this has to do with Atlassian? Could you have clicked on "help with Atlassian system" instead of "help with rootcoin"? Добро пожаловать в сообщество Atlassian! Не могли бы вы объяснить, какое это имеет отношение к Atlassian? Могли бы вы нажать «Помощь с системой…

What error do you get in the response?

Yes, licences are per system, not "this person can use the same software in different places". A licence for an Atlassian system is not given to the user. The licence says "up to X people can have access into this installation"

This is going to sound bad, because I am going to say the "not my fault" thing and not say anything about whether I think it is a good or bad way to go. Atlassian has never implemented a way to restrict people to create different types of issues. By project - absolutely, you can either create stuff in a project, or you can…

Assuming you're "won't do" is a "resolution", there is an easy fix - rename it in Admin -> Issues -> Resolutions. The harder bit of that fix might be up with a better name, but "cancelled" is a good option.

Team-managed boards can't do this, you need to be using boards created from existing filters (which you can only get to from company managed projects)