Nic Brough -Adaptavist- Expert

Did you start with a clean, un-worked on, set of issues? I suspect that the moving around you've done on the existing issues may be getting in the way.

And you may need to squint a bit at the one on the left to see the theme - RIP Charlie!

Nah, not here, I just keep it simple with a pile of identical ones, so I don't have to think about pairing. Apart from the odd random gift...

JQL does not have functions to look at permissions of users, so I'm afraid not. Alexander has given you the closest you can get without having to find an app or code new JQL functions

Also, you'll need to check the "create issue" permission.

You need to enable the global permission first, not look at the space yet.

Cloud premium already has the function to pin data in an area, and that's coming to standard subscribers soon. For France specifically, no, the data centres for Europe are Ireland and Germany (Dublin and Frankfurt from memory). So in the EU at least.…

Welcome to the community! Sub-tasks are not items that go into a sprint. Of course, they do really, but only because they are part of their parent issue, which can be in a sprint. The only way to get your sub-task into a sprint is to re-open the parent and bring that into the sprint. Or move the sub-task so that it is part…

Yes, there are lots of ways to "migrate", but we can't begin to talk about them until we know what you really want from a migration. Jira is an issue tracker, used for tracking stuff that needs doing Sharepoint is where documents go to die (This is a description I've stolen from a recent client who uses Sharepoint the way…

Welcome to the community. Admin rights give you admin, not "do everything" (which is a terrible terrible security model). You'll need to look at your rights within the project. As an admin, you'll be able to change them.

Welcome to the community! You will need to ask your administrators to grant you the administrator rights to create projects. Or get them to create the project for you.

Is the issue and all its sub-tasks (if any) in the very last column on the board?

Workflows are made up of two things - steps (each of which has a single unique status mapped to it) and transitions. An issue is created at one step in the workflow and to change steps/status, you move it through transitions. A step is a state of being, whereas a transition is an action (that changes the state of being).…

Your admins have not enabled anonymous access at the global level yet. It will appear in space permissions once they have.

I'd still go with "set it for them" in this case. But, yes, you'll need an app to provide a validator that can check what has been entered and tell them off for forgetting to set a field.

My understanding (bear in mind I don't work in the Product team) is that your people who are hitting this problem do not have the Confluence Space Permission to create/edit pages. The form gets saved as a page, so you need create/edit to save it.

Sorry, I didn't see your update at the time! I won't repeat what Earl said just now - he's given us everything I'd want to say.

Ahh, filter by sprint is the problem. Sub-tasks are not sprint items, and do not have a sprint field. They are only "in a sprint" when their parent issue is in the sprint and they're only there because they are a part of their parent. It is a long-standing flaw (in my opinion) that the sprint field is not automatically…

Welcome to the community! "Unresolved" in the resolution field is usually not actually a value. It is Jira finding the field empty and displaying "unresolved" to the humans, because that's what an empty resolution means - the issue is not resolved. Any value in the field means "issue is resolved". (Even if an inexperienced…

What are you searching for and how are you filtering?

Yep. There are some apps which can provide listeners to catch events and fire off webhooks, but you can do the basics with automation too. If you go to Admin -> Automation (or project settings -> Automation), and add a new rule, you should find a trigger called "when issue moved", and an action of "send web request" with…

Ok, there's several things in here! * In your first screenshot, at the top right, you do not have the settings cog which tells us that you are not a Confluence administrator. You will need to get that, or get one of the administrators to enable "anonymous access" in the general settings * Once that is enabled, you'll see…

It was a good suggestion, I should have mentioned it too. But it's not right for your case. It's a standard recommendation that boards should be for a team (in fact, if you look at Jira Align, you'd find it equates the two completely - a board is a team)

Have a look at the histories of the task and sub-tasks. I suspect you will find someone has changed the estimate fields directly, rather than logging work.

Go to Admin -> Backup manager and hit "create backup for Cloud". This will give you a file containing everything, which can be directly used to create a new Cloud system or overwrite an existing one (i.e. restore)

Assignee is a coded swimlane setting, like Story, Epic and Project, but you can also use "Queries" to define swimlanes. If you change from Assignee to Queries, you'll be presented with a list of name/query/description lines that you can add as many as you'd like to. So, you could easily do swimlanes like: * Alice's lane:…

Just to be clear in case someone else lands here - the important bit for your sprint is that burn-down only happens when an issue is "done". Jira defines this as "in a status that is in the last column on the board". It doesn't care what the status is, what the status category is (although that matters in the sprint report…

Kanban columns are representative of status. The only way you can make a column look like it is by assignee is by having a workflow that has status representing each possible assignee (which would no longer represent a process, making the issue tracking pretty useless) You can slice up a board by rows though, look to the…

How are you recording these relationships in Jira?

Try dropping the project part of the query and just ask "sprint = sprint1", and also check that all status are mapped into columns on the boards the sprint appears on, and all the status have categories (no grey "no category" status)