Nic Brough -Adaptavist- Expert

My guess is that you are looking at an issue that has sub-tasks with work logged on them, so it adds up to a different number than just the time on the parent issue (I can't see the image in the link, so I can't be sure)

The the list of available assignees listed in the assignee field is determined by the project's permissions. It is not determined by who the current user is. So, no, you can't do this.

The description of a field is not displayed on view because there's already a vast amount of stuff on the page and most of us don't need a field discription to understand the content. The description text is intended to inform people of what they should be putting into a field, it's sort of expected that a field should be…

This suggests you have a script that is broken. What is the script you are triggering with this action?

I'm afraid "I used ... no proxy..." and "doesn't use Tomcat" are completely incorrect. You only get this error whan you are using a proxy and you have not configured Tomcat correctly for https. You need to put those settings in the server.xml for the Tomcat that Jira is running on.

What do you mean by "suspended"? What have your admins done to cause it?

The best solution is to not build a bad process and try to implement it this way! That's what Cloud Jira has gone for.

Burndown is simple - you select a metric in the board config (time estimate, story points, or any other numeric field), and then burn down on cards positions on the board - last column is "done", others are not.

A transition can only result in a move to a single status. That is what they are for! I know our humans, and sometimes, robots, don't get the right transition and we want to trigger others when it's wrong. Could you tell us more about your case(s)?

How have you conffigured the email channel?

What do you mean by "container"? I am guessing you mean "Jira project", in which case, moving an issue from one project to another will change the issue key. It has to - the issue key must be unique, so the numeric part of it almost always has to change to the next free number in that project, and the issue key is made up…

Yes, I'm afraid Cloud can't/won't support it.

I believe so, but I don't know for sure. It's rare to see people change that - they usually know from the start which they want, and when in doubt, get standard and move to premium when they realise they want that, never going back.

These are the sort of errors we expect when there's something wrong with Java. What versions of Confluence and Java are you running?

It is not possible to disable the "pretty" urls without code change. See https://jira.atlassian.com/browse/CONFSERVER-52113 for the request. You can get at the id though. If you write a new "user macro", it can be really short: ## @noparams $content.getId().toString() (This is from memory, it might not be quite right, and…

Nothing more clever, faster or safer than what I have already outlined. There are a LOT of tricks you can use to minimise a lot of the work in the steps, but the basic "download and create server, merge, then upload" is the only way.

Yes, and get them working with Atlassian stuff. Have a read through https://confluence.atlassian.com/adminjiraserver/running-jira-applications-over-ssl-or-https-938847764.html and tell us what SSL strategy you choose, where you diverge from the guide-path that Atlassian give and what is going wrong.

Glad to help out! I hate this bug, it's really frustrating when you run into it, and it's really hard to explain. As that answer (which, unusually for me, is not a copy/paste/tweak) worked out, I think I might polish it up into a short article. Thank you for letting me know it was useful!

Exactly, that's why I suggested reading the answer.

No, they've not changed. The REST API simply replicates what you can do in one of the many ways you can ask the issue navigator to behave.

I am afraid we need more information on your systems before we can start to work out what might be wrong here. I will try to keep the questions short: * What plugin? * What responsiveness changes? * What processes have you crashed? * What have you looked at to try to fix this that might help? * What do you see when you try…

It would be a nice addition to the list of dynamic swimlane definitions though!

My guess is that you've run into a big bug in the workflow editor. For reasons that are a long and complex essay that I don't quite understand, you cannot add a transition out of a status that does not already have at least one transition out already. The bad news is that Atlassian are not going to fix this bug, because *…

Jira does not do this sort of field. One trick is to use the "table grid editor" app, which enables a table with variable numbers of columns and rows to appear as a single field. Or, the more common trick is to use sub-tasks - each group of fields (#resources, location, skills, etc) becomes a single field on each sub-task.

Have you checked the board settings for the field views on cards?

I'm afraid you can't do it without (unreliable and hard to maintain) javascript hacks, or changing the source code that renders the screens in Jira.

I've seen this when the source file to be parsed is invalid, or, more often, inaccessible to the user running it (either not in the right place, or with the wrong ownership or permissions). Check the file is where you expect it to be read from and correctly owned, and maybe try it with the full path to the file.

There is no way to change this. The project key is an integral part of the issue key, and should not be neglected. A search for 123 in one of the systems I've got would return thousands of results - -123 for all projects and -1123, -2123, -3123 etc for larger ones. There's simply no need for a search that works like that.

The burndown charts use the "estimation statistic" selected in the board configuration. That statistic must be a simple number (you can't do the required arithmetic on non-numbers), so the selection you are seeing are the three purely numeric fields you have in your system. Time estimates are one field that's always there,…

How are you doing test cases? Jira issue type? Jira issues with customisation? Test management app?