Nic Brough -Adaptavist- Expert

There is a very common misconception that "done" means "we did something about it and now no longer need to think about it". It does not. Exactly as @Trudy P Claspill says, "done" really means "we looked, it has been dealt with". Even when the action is "cancel, say there is nothing to do, or we're not going to do anything…

Welcome to the Atlassian Community! What do you mean by "folder"? Jira doesn't have such a concept, so I don't understand the question.

The "solution" is to not put estimates on non-sprint items. To show sub-tasks in the backlog, you can add the "sub-task" field to the backlog card layout in the board's layout settings. «Решение» состоит в том, чтобы не ставить оценки на непечатные позиции. Чтобы отобразить подзадачи в резервной копии, вы можете добавить…

You will need to talk to the MFA provider about it.

Are you using the same issue type screen schemes and field configuration schemes for the projects? Also, do the custom fields have the right context (they're global or set to show in all the projects you want the same layouts in)?

There is no issue here, you've rightly mapped your "needs no more attention" status into the done column on the board, because they are done. For reporting, you probably do want those different status, but you can simply report on the status instead of the column.

> Is it possible to use the group function in JIRA to create a group for Systems please ? What group function do you mean here? > And/or is there a way to group dashboards together ? Where? Dashboards are not project-specific, they contain whatever filters the owners have chosen to use in them, which are not limited to…

So why are you archiving pages you still want to use? Setting the default search option to "include archives" pretty much makes the archiving pointless. But you could get the effects - stop archiving pages you still want to search in the future and un-archive the ones you already have.

Sprint start/end is not really something you should be automating, it's supposed to be done by the team when they're ready. That's why there are no automation triggers for it, it's a bad idea to automate it.

Yes, you can have many "end" status in a company-managed project's workflow.

The only way to restore the issues with their old numbers is to do a full restore of the standard (not app) backup you took before you deleted them. That will of course delete anything you've done since the backup was taken. I'm afraid there's no way to change permission schemes on the free version. There is an issue…

I'm not sure comparing configurations is going to enable you to compare high-performing teams with others. A high-performing team will be using a scrum or kanban board to organise their work, with some good estimation process for sprint planning in scrum teams (no estimation in Kanban), a minimal set of fields, no…

I'm not sure that is even a Jira screen! When I click on "configure board", it goes to this: Then when I belt "edit filter query", I get the filter results and definition:

I'm regularly being asked to take up UK contract roles average about £600 a day for an Atlassian Admin, which would be around £90k if it were a salaried role. Bear in mind that all the numbers you are getting here are localised and you can't just translate them into your region by looking at the exchange rate. You can't…

Are the users retaining the issue key in the subject of the reply email?

You will need to write an app that can inject your new button into the menus, provide the new screen you want and do whatever else you need it to do. Could you explain what you are actually trying to achieve here, rather than just describe what you think is the way to do it. What are the users going to get out of this…

Schemes are global configuration items that you apply to compnay-managed projects. Team-managed projects are not configured with them.

Go to board configuration then general, where the filter is displayed, then you can click on that to go to the filter to edit it.

This usually means that you have not installed the current license on the server. Go to admin -> licensing and pit the new key in.

The board filter determines sort order on the board and in the backlog. It is usually set to order by rank, but you can change it to whatever you want. If you change it though, you won't be able to rank issues.

The "none" represents all the issues where the field is empty - they have no values selected.

Welcome to the Atlassian Community! We can not help you with this. Atlassian asks for 2FA when it is enabled, but it's not their system. You need to talk to the providers of your 2FA.

Welcome to the Atlassian Community! I am sorry, but I'm going to have to start with the basics. MS Access is absolutely not a database. It's a hideous half-arsed bodge that tries to pretend it is a database, but it really is not. So, yes, replacing it with anything that might actually work as a database is a good idea.…

Your script is not using the right account to make the request. @Chris Green nails the main reason for failure here.

There's nothing Jira does off-the-shelf for this, so you'll need to look to an automation or script that can read the current value and add one to it.

No, there's no way to amend these yet. I am not sure it is the right place for a confidentiality notice though - sticking something on-screen can not impose anything on the reader (most confidentiality and disclaimers are utterly worthless) but if it is just a statement about how you will treat their data (above and beyond…

Are you trying to do the horrible "multiple (current) assignees" thing that simply doesn't work in real life? Or do you mean you want to split up issues into fragments that can be given to different people (or even teams)?

Switching the heating back on and bleeding the radiators ;-) That's not really the favourite thing of course. I love the leaf piles we get in a dry autumn. Love dashing through them throwing leaves everywhere, especially when I can borrow a dog to join me! (We don't yet have a dog, but all but one of the dogs I know love…

Welcome to the Atlassian Community! Yes. Your columns are collections of status from your workflow (often only one status per column). To prevent people skipping the QA column, remove the transitions in the workflow that allow them to skip it. You've probably got a default workflow, where every transition shows as All ->…

:-) I'm not going to pretend I've spent a lot of time trying to understand the Kudos system. I do think it should be exponential, so the next level should be harder to get to than the current one, but I don't think that difference should be too steep a slope. The best levelling system I've seen was based on the Fibonacci…