Nic Brough -Adaptavist- Expert

You can probably jump Confluence directly to the latest version. I say "probably" because there's always variables that might break it. However, I have just been through a whole series of Confluence upgrades, 5.2 through to 7.4. We had some hiccups in lower versions, but if you've got an off-the-shelf Confluence, you…

You can't cast because the data types are incompatible in Java (not Scriptrunner or Jira). Use .doubleValue() to attempt the conversion, and see https://docs.oracle.com/javase/7/docs/api/java/math/BigDecimal.html

Do you mean Jira or Confluence? If it's both, then can you tell us what Confluence version you have?

The one that stands out to me is "unable to clean the (cache) directory". I suspect that if you look at the ownership and permissions of every file and folder in the Confluence installation and data directory, you're going to find that some files are owned by a user other than the one Confluence runs at, and hence they…

Neither really, changing the database like that will make it worse for a lot of queries, you'll just be trading one slow query for another.

<pedantic cough> Water, water everywhere, Nor any drop to drink.

I agree that it's a bit fuzzy, it is partly historical, and partly an apparent unwillingness to draw it all together properly on the Atlassian side (a reticence I don't understand). I keep meaning to write an article on it here. Logically, the right thing to do is have a single "done" - to keep plain Jira and Jira Software…

I've used XSLT to convert XML into CSV for imports in the past. I'm not aware of any apps that do it directly inside Jira though (other than REST endpoints in Scriptrunner, which I think are only available to Server, and writing my own Server "importer" plugins)

I do tend to avoid allowing "modify reporter" - I'll let automations use it, but for day-to-day human use, I stick with: reporter = creator = person who typed it in (or emailed it) because they needed it

The only "workaround" is "use a supportable protocol" - POP or IMAP (or, better, their secured versions) Exchange servers annoyingly make you jump through hoops to enable the decent open protocols now, so you could ask for your admins to do that, but the other option is to get a simple "forward email" set on the Exchange…

Oh, a listener! In that case, try def issue = event.issue

It's not in the slightest bit "stupid" - it is a clear, simple and unarguable definition of done, as Agile (and, for that matter, Waterfall) processes strongly recommend. The "bypass" is to put all your end status into the last column.

A backlog is not a container for issues, it's displaying them. The order in a backlog is only useful when looking at that backlog. You could have created this issue in many different backlogs, all in different "positions" in each one, and as soon as you create another issue, let alone someone start using the backlog to…

Ok, that's a bullet point I missed off! My script was written as a post-function - it runs when an issue goes through a transition. In post-functions, you automatically have the variable "issue" holding the current issue that the post-function is running against. I suspect you are running this in a console. If that is the…

I would guess that only one of those two status are in the last column on your board. Reconfigure the board so that both are in the last column and try again.

You will need one of the scripting or automation apps to go further than "issues under epic". But you shouldn't really do it because you should not estimate on sub-tasks. 

I'd say it's not finding an issue type named "Subtask"

There's no way to change the order in most places. Where do you want to change this order and in what way? And why?

What do you mean by "position"? Issues are ordered in filters and backlogs by the order of the filter or view. "Position", used alone, is useless because it is out of context. You need to look at how the list is ordered before you can say what the "position" is. Once you've got the context, the next thing to do is explain…

Look at the permissions for the project, the important one is "browse project". If you change that so it no longer includes the people you don't want to see it, the project will vanish from all their views and options.

To answer "why" (as Fazila covered everything else I'd say), it's a bit of history. Originally, when Jira was first written, when people raise issues, Reporter is the field in which you capture who is doing it. There was no concept of a creater - if you reported it, you created it. But, people started using Jira as a…

There are a number of reasons you might get this, but the starting point is to know whether you are on Windows or a Unix-like system as we probably need to be looking at the file systems, and they are very very different across the two systems.

Ok, that is what it says. You have landed on an issue for which you do not have permission to see, or it has been deleted.

Yes, they'll run in a development mode (no change to functions) For the previous comment that I missed - developer licences match your production numbers.

Ok, What does the application log say? It will be something like <confluence home>/log/atlassian-confluence.log

Jira does do XML and ANSI, but it needs to be structured in a way it makes sense to Jira. Edifact is the wrong shape because it's not for issue tracking. If your code can't do REST calls for some reason, then yes, you'll need to find something that can convert from your data format to something Jira can use.

An SR scripted field is a calculation and a display-only field. The easiest way to think of their timing is that they re-calculate their content when an issue is re-indexed. A scripted field that pulls the Epic date down to its children sounds simple at first, but isn't. You will need to place the field on all the issue…

The easiest way to points 1 and 2 is to have a field that holds that number. You'll need a scripted or automated field that can update on every new story, or change of epic link on existing stories. Then you'll be able to do JQL like "epic story count < 32", put the number on the cards, and use it as a sortable column in…

I keep meaning to get this added to https://library.adaptavist.com and never quite find time. Please note, * I'm not a proper coder, it probably could be more elegant * It was written for Jira 7.6-ish * I've not tested it properly on newer versions * My multi-select field is called "Animals" * It's minimal, creating issues…

Under the hood, the "global rank" field does maintain a single prioritised list. If you had a board for that had a filter of "every issue", you'd see the backlog in there matches the ranks you see in other board backlogs (assuming they're all using "order by rank") But boards have functions that override bits of it for…