Nic Brough -Adaptavist- Expert

The point of a backlog is it lists everything. A sprint is a time-box you say "we're going to get these items done in". In Jira, the backlog shows sprints because it's easy to plan in one place. Yes, you could call a sprint "to do", but when you complete it, what do you call the next one? If you're not going to use…

That really isn't going to work for you. Sprints are simply not backlogs. A better way to work would be to go with the way Jira does Scrum (or Kanban). It doesn't really matter if the issues are all in one project or spread across projects, as boards can draw from many projects. You need a rule for identifying when an…

Yes, your removed status doesn't exist for the issues any more, they have to move to another one in the new workflow.

So you've told the board to use story points for the (sprint) estimation statistic?

Yes, the issues will be "migrated", but that has less effect than it sounds. Jira will compare the new workflow with the current status of the issues. If the new workflow is missing a status that the issues have, then you will be asked which status in the new workflow you want to replace it with, and the issue will change.…

Welcome to the Atlassian Community! To do this, you'll need to set up the hierarchy globally. This requires you to be using Advanced Roadmaps (premium subscription). Also, it won't support your hierarchy as described, as you've got too many layers at the story level. * From the bottom up, Jira does* Sub-task (part of an…

I wouldn't do that - you're still confusing what the sprints and backlogs are by calling a sprint a backlog. A sprint is not a backlog, it's a slice of a backlog, and it's going to change. Look at it this way - at the end of the sprint, everything in it should be done. You won't be using it again for managing work. i'd…

You kept saying "done", not "last column". People often say "done" when they're talking about status or resolution, which is why I've repeatedly asked for clarity. What is the estimation statistic? What estimates did you have on the issues?

I think this is what is confusing you: I see multiple backlogs: [...] Question: What do you call those in Jira? We are calling them backlogs. These are sprints, not backlogs. You'll need to stop calling them backlogs as it is totally muddling you up. You're looking at one backlog, which is a list of stuff that needs some…

What column are they in?

Um, you can't actually do that. There's no such thing as "a board with multiple backlogs". A board has a backlog, that's it. The board and backlog are two ways of looking at one thing. So, I'm now very confused on what you are doing, as there's no way to have multiple backlogs in a single backlog. Do you mean you have…

Does the filter show you any sub-tasks if you run it in the issue navigator?

Welcome to the Atlassian Community! No, Jira does not have field-level security. Years ago, I was told they were never going to add it, as it's a collaborative anti-pattern, and Jira's sell is as a collaboration tool!

Welcome to the Atlassian Community! Backlogs don't belong to projects, they're part of a board. For certain types of project, the answer is "yes" though - you can create multiple boards that draw in issues from your proect and that board will have its own backlog, separate from the others you may have created.

Ok, you've also ruled out issue security, so there's only really filtering left. Have you applied a quick filter to your view? The other filtering thing is if someone has done something very weird for your board filter, configuring it to look at users dynamically (which will completely defeat the purpose of having a shared…

Welcome to the Atlassian Community! It's going to be a bit random - it depends on which email channel gets to the email first. You should not be pointing multiple channels at the same incoming email. I would question the reason for creating duplicates, but that's not going to help you unless you change your process so that…

The backlog (and its board) is not directly permission on the issue-level, their permission is a simple "who can use the board". A board/backlog is a view of a set of issues, not a container. My best guess is that the board is showing you issues from several projects, and although you can see the board, you can't see all…

You need to have admin rights on the board - admins can create new columns with whatever name they need.

You need to be a full Jira admin, not just the project admin, and it's a global setting under admin -> Issues - note the highlighted option in Carlos's screenshot

Welcome to the Atlassian Community! You'll need to talk to the owner of the page or space about getting edit permission for it.

I did say this in the answer, but I neglected to repeat it in explanations - the field context is about project and issue type. The same "if it's global, you won't lose it" applies to change of type as well as project.

Welcome to the Atlassian Community! When you complete the sprint, are the "done" issues in the "done" column (the last column on the right hand side of the board, doesn't matter what it is called)

Quick filters don't change what the board selects for. The two usual culprits of not seeing issues on the board are the board filter and not mapping status into columns. In this case, I suspect it's your board filter. Sub-tasks are not going to match "and fixversion =" - they don't have that field, it is implied from their…

Welcome to the Atlassian Community! You can call issue types whatever you want, but I would not recommend moving away from the standards much, it's confusing for people who've used Jira before. You can rename the Epic, if you have advanced roadmaps, but if you do, I wouldn't change it to anything other than "feature" to…

No it doesn't, it shows up to 50 people's issue creation. Most of the reasons I can think of for looking at a report that does this, I would generally only be interested in the top 10 issue creators - the question I'd be looking to answer is "why are these people creating so much more than others"?, I really wouldn't be…

I'm sorry, I should have been able to work that out from the question, but I was not sure. This message is telling you that you have tried to share a key with another account. That's a poor security practice, and one you should not do. If you can't remember what account the key was originally associated with, your best…

I'm afraid that's not how others read it. I didn't see it as bad as others, but it certainly wasn't constructive and it was written in a way that was asking for answers that you wouldn't like - condescending or asking why you're posting a rant instead of engaging.

Ok, that's actually great, in some ways. It means you don't have any cases where you might have data loss! If you move an issue from one project to another, Jira only deletes custom field data when the field does not exist for the new project. Field configurations and screens are irrelevant to that, it's only the field…

But what is the identity provider and how have you configured it with Jira Cloud?

No, because it's free for up to 5 users! See https://www.atlassian.com/software/bitbucket/pricing