Nic Brough -Adaptavist- Expert

I don't think it's directly the dashboard that is not working, it's that you do not know what you actually want from the reporting. You'll need to define what a "summary of all ongoing project tasks and issues" would be for you. We can then probably help you build a dashboard that covers it.

There is nothing to resolve here. Just leave them in done/completed and with a resolution set. You can ignore that status in most reports, queues and other places that only look at open issues, and still find them when you're activley looking for closed stuff.

You'll need to look at both emails and the two subscriptions the user has got set up for them, with a view to stopping the "wrong" one.

Assuming the "owner" of an issue is the reporter or an assignee, yes, you can set the permission in the project to "Delete issue: Reporter" or "Delete issue: assignee" Next-gen projects do not have this function though. I'd also recommend not allowing delete in general. Deleted issues are totally gone, destroyed and you…

No, it's not calculated for display at all, it's a function for comparing with issue data. Created date is available as a column in places where it's relevant to the display though.

It's not calculated for a display, it's just compared against the issue data. If you could get a result out of the function, you wouldn't like it anyway - startOfWeek() at the time I'm writing this would, if memory serves, come out as 1611014401

Sub-tasks are not linked to the Epics, their link is indirect - you need to look at their parent to establish which Epic that is in.

This sounds like you have "bought" two separate Cloud systems, instead of upgrading your free one from 10 users to 100. Could you confirm this is the case?

No, the path in the context must match the path in the base url and the path the proxy is serving up. You need to compare all three to find out which one (or two) are wrong.

The path in the context must match the path in the base url and the path the proxy is serving up.

Ok, there's some stuff to unpick here, but I'll keep it simple: >Someone on my team created a kanban board as a component of another kanban board This is not a thing in Jira, there's no "board as a component of another board". A board is a board in its own right, it has no form of inheritance, componentisation or link to…

Ok, so I'm guessing you can map the unmapped status? I suspec there is no "add status" because your board is using the workflow(s) provided by the project(s). The add status is only an option when you're using a "simplified" workflow for all the projects and issue types the board is covering. To get more status in your…

I think I can describe what you are seeing here, swimlanes showing you * Everything with a due date before today * Everything with a due date over 6 days in the future * The issues with a due date between today and 6 days in the future (although this would have been different between the 1st and 7th of January as the…

Do you have any unmapped status in the board config? When you say you don't get an "add status" button, and that you are an admin, are you a Jira or System admin? Not just a project admin?

I'm going to take a guess that you have forgotten to update the "Context" in the server.xml file. A standard upgrade will overwrite it and make your system behave as you describe.

No, is the short answer. Conditions are evaluated when someone is looking at an issue and looking for transitions. If you add a new one, then yes, it'll kick in and stop stuff straight away, but it has no historical impact. So the good and bad news is adding a condition does not cause any existing data to change - good…

You would not generally want to use status in swimlanes. Because columns are already based on status, you'll end up with mostly empty board cells and it wouldn't tell you anything more than a board without swimlanes at all. I think you might be mixing up swimlanes with columns - could you confirm what you're really talking…

Delete the project is the easy way. Slight more long winded - run a search for "project = X", which will give you a list of all the issues in it. You can then use "bulk edit" to delete them en-masse. You'll have to go 1,000 at a time though.

* It's more complex than that - Jira provides a framework for apps to work on, but in turn, Jira is running inside an application server (Tomcat) which in itself is then running inside the JVM. Not all apps run inside Jira, some run separately to it (but you'll spot these when you read the installation instructions for…

No, that's very very not how sprint estimates work. Have a look at how the time estimates work in Jira - you start with an original estimate, which then does not change (same as story points). As people log work (giving you time worked), the remaining estimate drops as more work gets done. With Sprint estimates, you…

When you create a new label for a page, you get a box pop up to type into. Can you tell us exactly what happens when you put something in there and click "add" next to the entry box? (Keep an eye on the labels area in the greyed-out background area - does that change at all? Even before you close the label dialogue?)

We can't help if we don't know what the problem is.

Um, no, that could easily fail, as you've not taken account of the caches. I don't think SR can even clear the cache you would need to hit. Your script could only work safely if you stopped Jira, restarted it, run the script before anyone starts using Jira projects, then stop and restart it again.

>when dragging an issue on the Kanban board to the "Done" column, remaining story points are not set to 0. No, they're not supposed to be. That's not how estimates work. If you set your estimate to zero, that destroys the point of estimation and all the reporting you can do on it. The only time you set a story point…

"for analysis" tells us nothing about why you want to change it, or what problem it us causing. Could you tell us what is going wrong in your "analysis" that is caused by this? Or more usefully, why your "analysis" is struggling with it?

Yes. You don't need to add it, it's already there.

It's before, during, during, during, but as the last part. Conditions run before the transition. They're a simple yes/no check, and if the answer is "no", then the user can't even start the transition. Screens happen next, as the transition is started, a box goes to the user to offer them the chance to enter data.…

A public system dashboard does not create a problem. That was the point. Anyway, yes, there is no point in continuing, you're not understanding it, no matter how many different ways we've approached it.

I can't think of a way to do that. The closest I think you can get is what @Carlos Garcia Navarro suggested - Column by status, swimlane by customer

It's useful because you seem to be struggling with the concepts, and other people landing here should not be left hanging with your misunderstandings. Please have another read of the earlier stuff. And then maybe answer the question of how you believe a pointless empty error message is better for the user that a dashboard…