Nic Brough -Adaptavist- Expert

You won't get an estimate more useful than "when it's ready" from Atlassian. Watch, comment and vote on https://jira.atlassian.com/browse/JRASERVER-67359 though - activity on there may give you some hints.

If the business doesn't want this doing and you don't know when they might change their mind, then it's totally unfair to ask you to try to plan for it. And you certainly shouldn't plan for it either. It should go back into the backlog, with a much lower rank than stuff you can plan for, and left there until they can make…

No, that's fixed I'm afraid.

Ok, so you will need to grant them permission to see the pages above the page in the hierarchy.

Nothing "official" (as in Atlassian product), but when you want a desktop app https://almworks.com/jiraclient/overview.html is the thing I've reached for in the past.

Which you didn't have in 2012

The easy answer with that is "with what?" But there's still a problem with "integrate" - it's a "suitcase word" that tells us something, but never enough to begin to answer the question beyond "probably". Imagine it this way - you have a suitcase with some things in it. You ask me "how do we clean the stuff in the…

No, that's the point, it does not have a physical workflow. It has a logical workflow built up from your configuration and (mostly) the columns you have on the board. If your smart commits are failing, then it's because one of the project owners has changed the configuration of the project (probably by changing columns)…

You should be able to see most of the details in the "orders" part of your account when you log into my.atlassian.com The email addresses for bills will be nominated in there as well under the "billing contacts"

So they can see other pages in the space? And can they see all the pages "above" the page they are not able to see?

The quick subtasks app adds functions that are essentially "click and do something that's part of Jira in the back ground". It does not record when it is used to create sub-tasks, to the best of my knowledge, so no, there's no way to know how widely used it is.

Do you have an error message? "Baulked" suggests it's just sitting there, but we can't be sure from that, can you describe what you see in the browser? More importantly, can you look at the log to see what that is saying?

You should not be putting the QA estimates on sub-tasks. QA should be part of the team, and hence part of the overall estimate for the Story.

I don't think you've understood how useful this might be. There is a request for it, closed through sheer lack of interest. Threaded comments are far more popular, but the fact that in 15 years only 3 people voted for numbering strongly suggests it's pretty much useless. Note that the conversations here are threaded, but…

You would need to ask your administrators. You have not said if you are on Server or Cloud though, so there's two different things you might be asking of them: If you're on Server, then have you been relying on the standard regular xml exports, or (as recommended for medium/large systems), are the backups a database copy…

To limit people to projects, you will need to amend the permissions for the projects you don't want them to see, removing whatever it is that allows them to "browse project". While doing that, you'll probably need to think about how you let the other people who should retain access back in.

There is no way to do that. A workflow for an issue type does not vary by group or rights. You'll need to look more carefully at what your users can see. My best guess is what you really mean is that you've put conditions on a workflow such that admins can do more than average users, and my backup guess would be that…

Boards are not containers for issues, they are a view. If you change (or delete) an issue via a board, you have changed the single object that might have been selected by many boards. Deleting an issue in Jira is a permanent thing. It's gone. Your only option is to dig out a backup or maybe notification email from which…

Again, Next-gen projects do not yet have workflows.

Next-gen projects do not yet have directly editable workflows, they follow the board. See https://jira.atlassian.com/browse/JSWCLOUD-17434 for the feature request.

You use the "Epic Link" field to do this with Jira Stories. This assumes you have created one or more Epics. It's also only a function of Jira Software, you won't see it if you have just have Core or Sevice Desk

hibernate.c3p0.timeout - I can never remember it until I see it!

As it's been a few days since you posted and you have no response, I suspect no-one who has read the question knows what MPLABX is, and there's nothing in the marketplace for it. You'll probably need to explain further, if you want us to help you to connect to it. A rough idea of what it is for, what you would like it to…

I think you've grasped a lot of it, but need more help filling in the pieces you don't need. Rather than try to do that piecemeal, I find it easier to explain from scratch. You have a pile of items that need doing. In Scrum, these are Stories. Jira uses "Issues" as the main word for these items, but you can (and usually…

If you mean a Jira account, you'll need to talk to your administrators. If you mean an Atlassian account, you'll need to log into id.atlassian.com with it, and find the delete option in the profile settings. If the account is the owner of any systems or has other data that needs to be retained for audit reasons, then you…

But there's a load of publically shared information Jira needs in order to function now. So you can't turn it off.

My guess is that you have not put your closed-something status in the last column on the board, which means "done"

I'd go with created <= -1w and updated <= -1w

That will break, quite badly, unless you change all the other places to match it. 

No, the heirarchy in plain Jira is Epic -> Story -> Sub-task. If you want more, you'll need one of the apps that enable more layers - Structure or Portfolio for example.