Nic Brough -Adaptavist- Expert

You are not going to get anything like that. The columns are based purely on status.

The hierarchy Jira supports is Epic -> Story -> Task. Advanced roadmaps will let you create layers above Epic, but not between the others. The closest you can get is to add the Structure app to your system - you'll need to have a think about whether to discard the Epic -> Story function completely and do it all in…

No, it expects you to do that with Bitbucket.

I'll take a slightly different approach to - why do you want to change this? What problem is it causing you?

No, it makes no sense. The question here is about hiding the system dashboard. The system dashboard is a good landing point. What benefit would you get from hiding it and effectively giving your users a dead end point? Instead of one that (can be or) is a useful starting point that shows them only stuff they can see,…

They can't check every detail on every app, but they do do some checks. In this case though, it's irrelevant. The spec for an app doesn't have to (and in some cases, simply can't) include "be able to be set on a project by project basis". That's not up to Atlassian to decide, it's up to the vendor.

Just looping back as I've had a conversation which reminded me - as @Walter Buggenhout said at first, the Community prefers positivity. Very early on, there was quite a long discussion about down votes that also mentioned marking things as wrong, and it was robustly rejected by the CAB. Historically, the older versions…

You'll want to follow through the +add request form It should let you map a new request type on to an issue type, or add a new issue type (I suspect complaints are probably going to be very differently set up to other issue types, so I'd recommend adding a complaint type) When you've got the new request/issue type pair, it…

The columns are being determined by the underlying setup in the projects you are creating the boards from. You're choosing a project type that has a default of the columns you are seeing when creating the project. I don't know what you're doing differently to before, whether the status in the projects are different or…

You will need to reconfigure the project so that it has the columns you want.

You will need to add that group to the space permission for viewing all pages, and then add the group to the page restriction(s) where they need access.

You need to move away from the fallacy that there are columns for scrum or kanban. There are not. Columns are determined by the project settings, not the board type. The columns do not determine whether a board is scrum or kanban. Your columns are coming from the project settings.

Please stop postinf random bits of errors without any context.

It's basing the columns on the status you have defined for the project.

Edit the workflow and check the transition from To Do to Done - you should find it names a "transition screen". You can change the fields on a screen by going through Admin -> Issues -> Screens. (Be aware screens may be shared by different workflows and projects)

It looks like you have got a Next-gen project with all the features turned off. The project admins should be able to turn on features like backlog, reports, estimates and apps from the project settings.

If you are on Server, then I'd suggest the use of a "scripted field". If you're on Cloud, you can still script fields, but you'll also need to ensure you remove them from the "edit" screen so that people cannot edit them.

Add a new request type? Or even a new portal (project) if complaints are going to be handled by a different team.

Umm. >A Kanban board should in my opinion consist of four colums (selected for development, in progress, in review, done), right? No. A Kanban board should consist of a set of columns that match your process. When you create a new board, it looks at what you've got configured in the project. If you're selecting "Kanban"…

Dumping an error message without any context on where or how is not a useful thing to do. We can't tell you anything other than you've got a broken or missing certificate.

I'm going to assume you mis-tagged this with Cloud and you are on server (as you would not see this sort of error on Cloud) It is what it says it is - the Confluence server process is running as a user who does not have full write access to /confluence_home/temp on the server. You'll need to have the server administrators…

This looks like it is right to me. The place you are entering "hari-5" is a text search - it's looking in the summary, description, environment, comment and other text fields. The issue key is not a text field.

https://library.adaptavist.com/entity/set-behaviour-hidden is a good example

No, the issue type icons are supposed to be a short at-a-glance representation of the issue's type, not it's status. They can't (and shouldn't) change on status change, you should be looking for the status indicators for that.

The columns do not determine whether a board is scrum or kanban. To do/in progress/done is the default set of columns for the boards in the project you are using. I think you'll find the board is still Kanban, just has different columns to what you are expecting.

The database behind Jira is not designed or intended for reporting. The SQL you need to run construct if you want to get the same list of issues a particular JQL query returns is torturous and slow, and it's rare that someone gets it right. In your case, you'll need to join the main issue type to at least five other…

Use the JQL function startOfWeek and/or endOfWeek Assuming your Jira is set for Monday as the first day of the week, then you'll want a query like created > startOfWeek("+2d")

For Confluence, see https://www.atlassian.com/software/confluence/pricing For Jira, see https://www.atlassian.com/software/jira/pricing For the others, have a look at their Marketplace listings 

Dashboards usually do solve this problem for most of us. What is your dashboard not doing? What do you want to see from a report?

The other thing you might be missing is the difference between the transitions available to the agent and the customer. Note that the rest call being made here is for the request transitions, not the issue transitions.