Nic Brough -Adaptavist- Expert

I think you are mis-naming things here, you are mixing up columns with swimlanes. Columns are groups of status (often only one status), they are vertical slices down a board. Swimlanes are groups of, well, anything you want really, as you can define them with filters. They run across a board. So, you say "I moved it into…

The smoking gun here is Could not open Hibernate Session for transaction; nested exception is net.sf.hibernate.exception.GenericJDBCException: Unable to acquire JDBC Connection That really does mean what it says - Confluence has said "Hi Database!" and got back either "network says you can't talk to it" or "database has…

Ok, yes, you're absolutely right in your explanations of "My need is to have fields visible or not based on the selection of another field on the same screen" - Cloud doesn't do that, not even with apps like Scriptrunner (yet. The products team are pushing Atlassian to build stuff that would allow them to do Behaviours for…

Yes, I've seen this a few times, mostly where the post-function needs to update a remote system and that can fail. In the cases where you can't validate before acting, the usual resort is "flagging" - add some data to the issue that indicates "I tried to do this, but it failed". Almost always followed up with a service…

The only way to "fail" a transition in a post-function is to crash it completely. It certainly is possible to write code that will always crash, but you really really do not want to be doing this. Post-functions are not expected to break like this, they are expected to do things as part of a validated and successful…

I'm afraid this question is utterly unclear. The reason is you say "Platform Affected: [website] https://vzmdev.atlassian.net" and "Jira Version Used: 8.13" which is nonsense because the site is Jira Cloud which is emphatically not running Jira 8.13 Server/DC. Which one are you really asking about? Your Cloud site, or a…

Ah, I see. They're not "custom fields", they're built-in. You can't remove those, they're hard coded. Completely agree that they look goofy, I've rarely seen people put data in them, and I've never run into anyone who actually uses the data that goes into them! I think they're just a hangover from early Confluence when…

As John and Jonas mention, your "order by rank" will make the priority sort completely redundant. It is not as simple as this and doesn't work this way in the background, but you can think of the rank being a unique value. Unlike priority, you will never have two or more issues with the same rank. So if your first sort is…

Ok, sorry about this, but @Kristian Walker _Adaptavist_ has told me stuff about Scriptrunner Enhanced Search that I did not know before. There is an "added after sprint start" in there. I quote: You can now do addedAfterSprintStart in SR cloud enhanced search queries and the docs for this are here

Nope, not on the roadmap. Linkedissue and linkedissues() are already built in. See https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-functions/ You don't need Scriptrunner or any other app for this (although my marketing people would kill me if I didn't mention that Scriptrunner adds a…

Personally, I tend to use tools that won't bring them across if I don't want them, but I think you're using JCMA, which doesn't give you the option. Deleting after migration is probably the most simple thing you can do here.

You are right, issueFunction is a Scriptrunner for Server only, we can't (yet) implement it in Cloud. Some of things it was used for on Server can be achieved, there's a list of popular translations over at https://docs.adaptavist.com/sr4jc/latest/scriptrunner-jql-keywords-functions/jql-keyword-examples But I don't think…

Not for Server - the REST API doesn't have the admin functions you need yet. You'll need an app that can provide REST endpoints to do that work, or even replace whatever you're doing externally completely.

So I would start by renaming the link types - they're misleading you and your users, this is not a parent/child relationship. You will then need to write some code that can read links, following them to the other end to look at the linked issue and update its fields if you add or change relevant data on an issue. If you…

Boards do not contain issues, they are a selection of issues, based on a filter. This is often "project = X" but could be anything (some boards have fixed filters you can't get to) This make the word "move to board" completely inappropriate as a description of what you need to do to make an issue drop off one board and…

Be aware that changing the version of Java under your Bitbucket is not recommended, as Atlassian only supports you running on the Java that was distributed with the version of Bitbucket you're on. An upgrade will change the java version if the new Bitbucket version uses a later releases, so it's a good idea to go this way,…

Bitbucket Server/DC does not have pipelines, you need to hook it up to your build servers before you'll get options around the builds appearing in that menu.

"all watchers" is not a group, it's a dynamic "role", like "assignee" or "reporter". It refers to the list of people named as a watcher on the issue. To "modify the group", you will have to edit the watchers on each issue. There are no watchers on projects, it is just issues you watch.

I suspect what has happened here is a compounded problem. I think you've tried to start Jira up as the wrong user, then one of your system admins halted the system, which forcibly killed the process. You've then tried to start it again as the right user, but because the other user has taken ownership of some of the files,…

Jira Cloud is probably the most actively developed product Atlassian has. There's a new release around every 6 weeks (although the frequency is quite variable) It has a lot of ways of making fields visible, hidden, optional or mandatory and even using different displays, in the company-managed (classic) projects, with…

https://confluence.atlassian.com/doc/edit-in-office-using-the-office-connector-170493096.html explains what it does. I'm a bit stuck on understanding what you are looking for here.

Atlassian don't have people who do that sort of sales support. Generally, you would look to a partner to have those discussions, or ask questions here on the community if there's not a huge amount of them.

I do not understand what you mean by "integrating it". 

I don't think my answer in the old question says anything about "why", it's more about getting someone past a block or confusion. They "why" is better answered by "history and iffy design". Field configurations and screens were the approach chosen (if memory serves, for Jira 2) but you'd need to ask Scott or Mike exactly…

See https://confluence.atlassian.com/doc/edit-in-office-using-the-office-connector-170493096.html

You will need to fix whatever it is that is stopping startup. First, you'll need to identify it. You may find the command window that "atlas-run" is being run in is throwing you a lot of data which will tell you what the problem is. If not, then you'll need to start reading the log files the service is generating - those…

See https://support.atlassian.com/security-and-access-policies/docs/understand-data-residency-and-realms/ 

70 miles into London, a miles from the house to the station here and the other 4 were a guessed average wandering across London - the nearest I've worked to St Pancras was 1/4 mile, the furthest about 5 miles. Most were around 3 (the City, Old Street, Waterloo, Victoria etc) 

Or forget the idea of "move" as it's not right, and just look at what the boards are selecting, then edit the issue to match.

I am not quite sure what you are actually doing here. You can't create sub-tasks of sub-tasks, you are not doing * Story01 (Main story)* Design (Subtask of main story)* Task01 ( Child of subtask) * Task02 ( child of subtask) Do you mean you are doing something like linking the issues? So you really have * Story01 (Main…