Nic Brough -Adaptavist- Expert

For standard or premium Cloud systems, each user will need a licence for each system. However, check out https://www.atlassian.com/licensing/cloud#cloud-enterprise - the enterprise licence is aimed at your situation, with multiple instances and users.

Yes, the id of a field is variable by system. Unless the test system is a direct database clone of the production system.

You could wait for the data-lake to become ready, then you probably won't need to worry about exporting to an external database. In the meantime, you'll need to extract data over the REST API - https://developer.atlassian.com/cloud/jira/software/rest/intro/

What do you mean by JCL?

Bitbucket has not been called "Stash" for years, so I think your training might be a bit out-of-date. But yes, Bitbucket is a good way to manage git repositories, giving you a decent web-interface on to them and easy graphical configuration of branches and merges and the rest. Your team can use whatever they like to check…

I don't think the field id in your code is correct - "gremium date" is not system field, it's a custom field, so you should be using the key for that. Go to your list of custom fields, find gremium date and hover over, or click, one of the edit/configure options. You should see a url that contains "id=xxxxx", with the…

Ok, thanks for explaining the underlying problem. A popup or asking for human intervention is a bad solution to this problem, it won't help much, other than telling your people that they're about to lose their system for a while very soon, so they're just as inconvenienced, but slightly less surprised. You should be…

I think you're in the wrong place here. Greenshot is not an Atlassian or Atlassian related (marketplace) application. My best guess is that Greenshot uses Confluence and/or Jira for documentation and/or issue tracking, and you have clicked for "help with the Atlassian product" rather than "help with Greenshot or help with…

Ah, no, the "anonymous" group is not a group, it's inserted by the code and handled differently. You should remove the anonymous group you have added, as it is misleading. It has to be done that way because a group is a list of users, and the point of "anonymous" is that you do not know who the user is - you can't put…

Sorry, that can be confusing and I forget to explain it sometimes Confluence has a "home" directory to hold its working data in (things like the attachments, index, log files, backups, temporary files and so-on) This is not a *nix user's home directory, it is a dedicated directory for Confluence which could be anywhere you…

Roadmaps rely partly on Epics to provide the structure by default, so excluding them means it has nothing to work with (I don't think the sub-tasks matter, as they're right at the bottom level and don't contain anything lower). I would try it again with just "type != sub-task". Then have a look at the hierarchy settings…

What does "not working" mean here? When you click the "reported issues" button, does it take you to a list of issues? If so, are they the issues reported by this account? Is it the wrong list, or is it not going to the list?

This is usually (but not always) that the server is underpowered or struggling with resources for some reason, and it's simply not able to get everything done before the standard timeout. That needs to be ruled out first, so have a look…

In theory, yes, you could pull the Jira or Confluence out of the Tomcat and push it into another one. But I'm afraid Atlassian don't support that and it's not a simple redeployment, it is quite a lot of work. I also have a couple of third-hand reports from people who have tried to redeploy Jira on to Tomcat 9 have met with…

This sounds like you have an Apache proxy server in front of your Jira, but you have not reconfigured it to support the new location for your Jira.

I'm well aware of the Agile principles. I am not trying to say "you have to do it this way", or that there's anything wrong with what you're doing. Simply that if you have stories that are larger than a sprint can handle, you're not doing Scrum. But you're using a Scrum tool to try to represent your non-scrum process. So…

That basically means you are not being Agile at all. The whole point of the sprint idea is that you deliver within a time-box. You have headed towards the right way to do it though - split up the stories so that they can fir within a sprint. That's what Scrum recommends instead of having stories move across sprints because…

Confluence can only run on a single URL. You will need to choose one and use it consistently.

My initial guess is that this is the problem: >for my confluence instance have 2 url I suspect you've got your proxy config mostly correct for the external site, but then it's going wrong because your Confluence base url is set to the internal one. You will need your Confluence, Oauth, the proxy and the rest all to be set…

Switching databases isn't too complex fortunately. Install or find a database server, set up an empty database configured for Jira, get an xml export of your current Jira, repoint it so the empty one starts up ok, then import the xml. The longer version (worth a look as the bit where you commission a database is dependent…

As you have more than one Jira application, you may find you need to blank out the licence keys that are blocking the others - for example, if you're trying to install the DC licence for Jira Software, blank out the Jira Core and Jira Service Management server licences first, apply the Software DC licence over the Software…

An issue should always be available at https://<yourbaseurl>/browse/issue So for yours assuming you are on Cloud as tagged, and your organisation is named "Dave" (everyone knows someone called Dave), then https://dave.atlassian.net/browse/CON-10049 should do it. I'm assuming you're wanting the url, not one of the other…

Confluence only tries to write a confluence.cfg.xml file when it is being installed. If it is an upgrade, it leaves the file alone, but needs you to update it to include the new pooling requirements (among other things) - this is because the upgrade can not know and hence deal with everything you might have tweaked in…

Lower down in the error message, there are a load of references that tell us that your system is using the embedded h2 database. This thing is for demo/dev/test purposes only - throwaway instances that you don't mind losing and having to rebuild if needed, they're not fit for production because the h2 database can fail…

Ok, there are still a couple of things to look at. First was the bit from my original answer - are your scripted fields being pulled from a different issue? If they are not, then you may have a random problem where you have no way to know which field will be populated first. As above, if you have fields A, B, C, D, with A…

On server, we've got some options for "canned responses", although I, of course, lean towards using Scriptrunner to do some of it. For Cloud, I find people using https://marketplace.atlassian.com/apps/1211016/canned-responses-pro-templates-for-jira?hosting=cloud&tab=overview when they don't quite want to automate. There…

I am sorry, I am not able to make this clear. Why do you think you want to do this? What benefit is it? What problem does this solve or help with?

I would guess that your fields don't hold the data in the way you're expecting them to. Two things to do: * Look at both field definitions in the list of custom fields - what type of field is each? (Number, date, date/time, etc) * Brute force - try returning each value (toDoInt and inProgressInt) while testing the script.…

Raise a support request with Atlassian, they will change the name for you. It takes a few minutes when they do it, so you'll want to book a good time when your people are not using it much, and warn them about it of course. (Atlassian will not do this frequently, so make sure you choose a good new name. My memory says "not…

>splited in many subtasks, each assigned to different people, in the same sprint? If those are not available in the backlog, then how can we plan the sprint without seeing those Sprint planning is choosing what stories to commit to in your sprint. You do not commit to doing sub-tasks, they're part of a story. Sub-tasks are…