Nic Brough -Adaptavist- Expert

You will need to write a Confluence app that provides your search and plug it into Confluence. It will be able to turn off the inbuilt search and provide its own search UI. If you are building it for Cloud, then you won't be able to completely remove the Confluence search, but you will be able to hide most of the links…

Deleting status from a flow is different to changing it. You can't delete a step from an active workflow because there might be issues currently at that step. You must migrate them all to a different workflow before deleting a step, otherwise you'd render your issues useless and unmoveable. You will have to do what it says…

Confluence doesn't do dashboards at all! What you are talking about is Confluence pages being used as dashboards. It's not what Confluence was built for, but it's certainly not a bad use for it, and a lot of people do this. It would be great to be able to be able to create pages as dashboards, I think it would be a great…

Welcome to the Atlassian Community! This sounds like a problem with your account, and one that the community cannot help you with (beyond suggesting you to try clearing your browsers cache and restart the browser) you should raise it with Atlassian direct. Go to Trello.com/contact and use the "contact support" option that…

Um, that's what you said you wanted to see. But that is just the way I read your question. Could you write your search out as you would explain it to us if we were talking? " extract linked issues and issues under the EPIC "ABC"" is a bit hazy in Jira speak. Sub-tasks and "intake" are linked issues in Epics, linked issues…

Welcome to the Atlassian Community! If you no longer have access to your email address, then you can not reset the password on your Atlassian account. I am afraid you are going to need to create a new Atlassian account and ask another admin to add it to your Trello.

Welcome to the Atlassian Community! Sub-tasks do not appear in backlogs in Scrum boards because they are pointless noise. You can't rank them outside their issue (they are part of their parent issue, not separate entities) and you don't use them in sprints, so they are of no use in the backlog. On the board, you'll see…

Welcome to the Atlassian Community! You can't do this. The pie chart only works with fields that have a defined (and hence countable) list of options. Story point estimate is a numeric field with a an unknown range of possible values, so it can't be counted.

Welcome to the Atlassian Community! Feedback is what comments are for mostly. If you mean some form of rating, then have you tried adding a custom field for that? Or a dedicated text box for long text feedback?

A project can only have one issue type scheme. The issue type scheme tells a project what issue types are available to it. It's complete nonsense to have many - which one would you use to determine what issue types are available when someone clicks create? Or what to do when someone tries to change the issue type? If you…

Welcome to the Atlassian Community! Support projects can only be linked to a single knowledge base, so that the agents and customers get to see the same thing. You will need to document your stuff for the agents in a separate space and educate them to look at it for internal self-help.

Yes, you can edit the workflow and change the status in use. You don't even need to do any migration if you just change the status.

Security levels have nothing to do with anything that someone might do with an issue other than their ability to see them. You need to be looking at the permissions in the project - they control the edit (and transition, and assign, and comment, and and and) abilities. Security levels simply hide issues from people not…

There are no docs for the status - the status names pretty much are the documentation. When it says "config change", someone has changed the automation. When it's "in progress", the automation is currently running. "Success" means "ran without problems". And so on. What are you looking for from this documentation?

Welcome to the Atlassian Community! If a field has a global context, then the problem is with the screens, field configuration, or layout. For a company-managed project, look to the screens and field configuration, for a team-managed project, check the issue's field layouts. (Note that for company-managed projects, it's…

They review it regularly, but there is absolutely no intention of changing it.

You will only pay for the active users you migrate into the Cloud. Inactive users won't be chargeable for, but you'll want to make sure that you keep them inactive when you migrate. The worst case is you import 80 people, and it will look like you have to pay the first month for them, then make them all inactive so that…

Welcome to the Atlassian Community! Jira Cloud does not have its own internal users, it uses an Atlassian account, a Google account, or an Account provided by Atlassian access. You can't delete users in Jira, you can only remove their access. You can delete users in the user management system you have configured for your…

Welcome to the Atlassian Community! Cloning an issue does not clone the workflow. It clones the issue. The new issue will exist in the same project and, of course, as a clone, will be of the same issue type. The project and issue type being the same means that it will be configured to use the same workflow. You cannot…

Your query would work if you used parenthesis to make it clear to the computers what to do. At the moment you're including sub-tasks and intake type because Jira has no choice but to read the query left to right, it's not doing the and/or things the way you are thinking. I suspect you really mean is ( issue in…

Welcome to the Atlassian Community! Jira was built as an issue tracker, and later brought in code to support Kanban and Scrum. It has never been intended to be an Agile-at-scale tool, this came along a lot later than Agile (I've been working with Scrum and Kanban teams from before the Agile manifesto was written, and Jira…

Yes, this tends to mean that your database is either incorrectly configured, or corrupt. Jira is trying to insert new data that already exists in the database, so it is unable to do it. The most likely cause of this is someone editing the database directly, instead of doing it in Jira, but other things can do this,…

Yes, you are missing the big picture. You do not know what you are looking at. You are looking at a database that isn't even a Jira one. You have no access to an Atlassian-Cloud Jira database, so you're not replicating anything from an Atlassian Cloud Jira (because you can't). If it's a Jira server or DC installation, then…

Yes. By "standard fields" I mean the issue fields that are part of the core issue (and custom fields that you have added, as the custom field functions are standard). Summary, Description, priority and so on.

You can have fields required and importable. You just need to provide data for every issue being imported in a required field. Because it is required.

Not in the slightest bit essential, and potentially illegal in places. Have a read of my earlier essay.

No, there is no way to rename buttons. You would need to get the author of the app to change the language in it, or code for a way to let you do it.

No, Compass is not Open Source, it is an Atlassian product. Atlassian is not bad at open-source, they offer cheap or free licences to support open-source products, and when they decide to lose a product, they release it at open source. Compass is quite new to Atlassian, it's not going to be OS for a long time, if ever.

How are you doing the Oauth?

I do not really want this to be an answer because it is not a good one. But yes, Scriptrunner can do it. We need a bit of code, but it can do anything you want. A list of users is not a problem, but could you tell us why? ("all users" is a perfectly valid answer to that!)