Nic Brough -Adaptavist- Expert

We took some lessons last August/September/October. We got a couple of prizewinning ballroom dancers (Chrissy's employer and her partner) to teach us a simple waltz, so we didn't embarrass ourselves during our first dance at our wedding in November.

No, locked fields are not something Atlassian are looking at.

Welcome to the Atlassian Community! Jira does not have field locking functionality.

JQL only searches for issues, it does not look for users or access rights. You'll need to work through all of your permissions in all of your projects to find this out.

Welcome to the Atlassian Community! You do not need to write automations for this. Jira will move incomplete issues to the next sprint automatically when you close the current one.

So your rejected status lands in the last column? Are you excluding it somehow?

For which project types? And why? What question would it answer?

Welcome to the Atlassian Community! Yes. But what do you want from this "integration"?

How have you defined the last column on the board? Does it include the status you put things in when they are "rejected"?

Welcome to the Atlassian Community! JQL finds issues, it has nothing to say about how they are presented in whatever you are reporting them in. You need to look at the reporting functions - does the one you are using have any grouping functions?

It varies by the project type. Why do you think you need this? Is there a problem looking at the permissions for a project?

No, conditions are only there to limit people, not allow them. You always need "transition issue" permission to transition issues.

Welcome to the Atlassian Community! You'll need to look at how the IIS server is configured. Jira doesn't need a web-server, but most of us do configure it to use one at least as a proxy.

How have you defined the last column on the board? Does it include your "rejected" status?

If you don't want people to use a specific issue type, the best option is to simply remove it from the project. For Cloud, the best place to ask for feature requests is by following the "help" links in the ? menu at the top right.

Welcome to the Atlassian Community! You need to adjust your workflow so that it sets a resolution, either by asking a human via a resolve screen, or with a post-function that sets one. After that, you will need to push your issues through one of the workflow transitions that do it.

Hi Enes, There's no way to turn that button off on Cloud, it will always be available.

You can click on the connect link it has in the error message if you do want to set up a connection. Otherwise, visit Admin -> application links, you should be able to turn off a basic connection in there, or visit Admin -> manage apps and disable any github apps you have.

Moving issues should never be part of a standard process, it's for housekeeping and mistakes only. Moving an issue from a support (ITSM) project to a non-itsm project is always going to lose the request, non-ITSM projects don't have them. Moving between projects is also minimal because it should not happen often. If you…

This is the server asking you to complete the setup of the connection you have added to it. You need to complete the setup or ask your admins to remove the connection.

Mistakes happen, but the question remains as to why you have set it up so that people create things in the wrong place.

Hi Raphaël, No, there's no way to do this. You can't remove an issue type from the creation option without changing all the current issues of that type to one that you want to continue to create. The best you can do is change the workflow for issue types you don't want to use to one that has an impossible condition on it,…

Welcome to the Atlassian Community! Jira does not expect you to be moving issues, it's an exception to normal working practice, and the request type has nowhere to go if you move an issue from an ITSM project to a non-ITSM project. Why are you moving issues?

Welcome to the Atlassian Community! On server, you have an admin -> system information page which will summarise a lot more information that what you're asking for here.

Dashboards are not boards, I'd suggest you have a look at boards instead of dashboards.

Welcome to the Atlassian Community! A simple way to do this is with the "include" macro. If you create page 1 with all the content you need, you can put "include page 1" macro on pages 2, 3, 4 and 5. When you amend page 1, then 2, 3, 4 and 5, will all reflect all the changes the next time they are loaded or refreshed.

Welcome to the Atlassian Community! An issue is only "done" when it is in the last column of the board. If your issues are truly "done" when "marked for release" (as far as the current team using the board is concerned), then map that status into the last column on the board. The last column means "this team has no more…

I did'nt really want to call it out directly, but yes, the problem is more about your analyst behaviour. They need to be thinking of which audience they want for their comments every time they post (probably meaning talking to the customer a bit more!). Jira does make it very easy to do internal comments only though, and…

Hi Governança The resolution field is a global list of possible resolutions. As an admin, you can go to Admin -> Issues -> Resolutions and edit the list, renaming, adding, or deleting what you need to. The default list is not a bad one, but it is very generic, aimed at covering most people, not people who have highly…

Welcome to the Atlassian Community! There's nothing to fix here, the display is telling you what you really need to know. If an issue is "done", that really does mean "there is no more work to be done on this", so you no longer care what the estimate was - it's effectively 0 because you've finished the issue. If the story…