Nic Brough -Adaptavist- Expert

If they have not published contact details, then you'll have to use other sources of information - who asked you to use this Jira? Who gave you the account? Do you know other users who may know who the admins are?

You should not be "expecting" to have this. It's still a logical impossibility given the shape of the data, as I explained above.

I can't think of a report that would give you all the numbers in one place, let alone one that would do it in percentages. Closest I can get is: >Number of issues per user per project which are overdue This is possible in one place - you already have a filter for "issues overdue", so you can use the returned list in a…

Not quite - it can't read html directly. See https://support.atlassian.com/confluence-cloud/docs/import-content-into-confluence-cloud/ for your options

I think you might have clicked on "help with Confluence" instead of "help with the things that are being written about in this Confluence installation" You'll need to ask the authors of your documentation, not the Atlassian community (us) about this.

There's a long-standing bug in the draft workflow editor. You can't add transitions to steps that don't already have one outgoing transition. You will need to copy your workflow to one with a new name, and edit that. The inactive workflow editor allows you to add transitions to any step, no matter what. Once you've added…

Ok, Team managed projects don't do card layouts that way, the options for views are done from the options available while viewing an issue.

You do not. Because that way, madness lies. You should never never never have more (or less) than one person as the person ultimately responsible for an issue. It is of course, absolutely fine to have other people who can monitor, be involved with, and take over from the assignee if they're not around. There are many ways…

That statement does not give us anything to work with. Which board feature? What are you expecting and what does it do? What have you tried? What are you trying to achieve?

What type of project is it? (Team or Company managed, and is is Software, Service Desk or Core/Business)

@carrie_eandm - last time I went, there were three ways to get from the dock town (I'm sorry, I can't remember the name) up to the top of the rim of the crater so you could walk or ride to Thira and Oia - a zig-zag road you could walk or take a donkey ride along, or the cable car. From memory, my sister took the cable car…

I suspect Confluence is being used to document whatever mmsoc-xpro is and you've clicked on "help with Confluence" rather than "help with mmsoc-xpro" I'm afraid you'll need to ask the authors of the docs, we're not them.

The first few letters of an issue key are the project key. To retain them, don't change the project. The numeric part after the - symbol are a sequence. This also won't change if you remain in the same project.

No, the schemes and components you're looking at are all project dependent, they make no sense outside a project. If you're doing holiday requests, why aren't you just using an issue for it? That way, you get to use all the stuff you're asking about automatically. And you don't have to write an entire issue-tracking…

This can be due to different directories, removed users or historical accounts. It's going to be almost impossible to work it out from the raw database. This is one of the many reasons it is not recommended to use the database for any reporting - it's not built for it, and the SQL is horrendous. What question are you…

Yes, you can proxy the url directly as well, but this may have more faults than just hitting the url of the server. Admin should still be ok, but I wouldn't use it for anything else!

No, requests are a function of Service Desks, you can't get them for non-Service Desk projects. Generally the route to development is for a customer to raise a request, the Agent realise it's something that needs development and use "create linked issue" in the development project.

Welcome to the community! From the tools menu on the issue, select "move", it will ask for a project and issue type to move the issue to. (Probably just leave the project as it is?)

You'll need to talk to your space owners or confluence admins about this. I think you may have clicked for "help with Confluence" rather than "help with THIS confluence", and that click has brought you to the Atlassian community. We can talk about Confluence a lot, and there's a LOT of us with lots to say and help with.…

No, this has not changed. Any issue type can have any sub-task type. You identify what a sub-task's parent type is by looking at the parent. There's scripting and automations that can help if you put a bit of effort in, but I find them clunky, and it's easier to just educate people to raise the right type of sub-task, or…

And what are you doing about the open issues that are resolved?

The original and remaining estimate fields are actually aspects of the same field, but: * Original Estimate = the estimate on the current issue * (Sum of) Original Estimate = the estimate on the current issue added up with all the estimates on the sub-tasks of this issue Same sum is done for the remaining fields. Note that…

You cannot and should not do this for normal users - it will break in interesting ways. Everyone should use the same base-url (i.e. the one fronted by the load balancer) But each of your nodes has a separate address and you can simply use that (from a machine that is behind the load balancer, or bypassing it). If you've…

You could do that by injecting a web-fragment into the screens (My guess is that the system you mention had ScriptRunner, which lets you do that quite easily - it does web-fragments with a simple "where do you want it, what should it look like, what happens when it is clicked" config, and that "button" is probably just a…

Sub-tasks are not sprint-able items, they are a part of stories (which are). You don't commit to sub-tasks, you commit to doing the stories, and estimates measure commitment vs delivery. There are a number of ways of doing estimates on sub-tasks, but Jira has taken the simple route and does not support them at all. In…

It's important to understand that a board is not a container for issues, it is a view of a selection. If you want your boards to select for different issues, you need to tell them to select different things. Using your simple query as an example, you can have an issue appear on one board and not another by doing something…

A filter is a "saved search". I wasn't pointing at any filter in particular, just saying that you can use the "category" field in them if it might be useful (and Advanced Roadmaps does use some filters)

So you're happy to corrupt your data, have unresolved issues that are resolved? Atlassian support did not provide you with this solution. They will have told you what I said before - you can put the resolution on the edit screen temporarily and remove it later, before you corrupt your data.

You can use it in filters - "category = client" in our Jira for example will return all the issues in projects we've classified as "client projects", without having to name each project. But no, I don't think it's usable in Advanced Roadmaps in any way other than the filter clause I've just mentioned.

No, this is exactly what we said you should not do. It will corrupt your data. Again, if you put the resolution field on the edit screen, then every edit will resolve your issues. You will be corrupting the data on every edit. Please see my answer and last comment in the thread from the 27th April.