Nic Brough -Adaptavist- Expert

That won't affect the upgrade. But it does make a good point - 6.13 is end-of-life in 2 days, you should be looking to upgrade to a supportable version, probably one of the more recent LTS versions.

Jira field configurations are determined by the project and issue type, not the team or people using it. But you can do this because you have the teams working in different projects. That means you can do stuff like "In project 1, use config 1 for bugs and in project 2, use config 2 for bugs". The issue type screen scheme…

No, Atlassian don't do that type of support, you would need to engage with a partner. Atlassian support on an upgrade is limited to help when something goes wrong (probably in your test run) and you can't fix it yourself.

Again, you can't change the list of options in a select-list field with a behaviour. You can only add or remove existing options.

What backups were you running? By default, the atlassian stuff runs regular simple xml backups regularly, so if you just installed and ran with them, they probably have backups you can import into a new clean system (server or cloud). For Jira and Confluence, the backups will be zip files under the export/backup…

Go to your my.atlassian.com account and add the new owner as an admin. Then get them to do the same and remove you.

It sounds like you have created a select list field to hold the data being read from another system. This won't work - select lists draw their option list from their config in Jira, you can't change the option list with a behaviour

What app or process are you using to try to get the two of them to talk to each other?

How are you doing this integration? You've not explained what you are using to connect the two.

This means you have put the issue type "field" on a transition screen, but there are no issue types in this project with the same configuration as the current issue type. In other words, it's telling you why the issue type "field" is not listing any options

So whilst this could be read as a performance or complexity question, I would say that we've moved on. When I started using Jira, yes, having a massive pile of status could have a measurable performance impact, so I was always pushing to cut it down. <mumble> years later, I would say that each new status still imposes the…

See YTZ's answer and my supporting comment.

Good question, I didn't put that into the story, but imagine one of my days at that job as an example: * 7:44 - get on train, code/email/document for a while on the journey * 9:30 - work-log timer started, on issue xyz-123 * 12:30 - work-log stops as I pop out for lunch * 13:30 - work-log timer on xyz-123 started as I get…

@Bill Sheboy - I do like that "there are no best practices" statement. I regularly get asked for "best practices" training or implementations from clients. I don't blame them for asking, it's not a bad way to ask for "tell us how to use the software well, take advantage of what it can do, and avoid doing bad or clunky…

My guess would be that it's a human-tracking plan. One of my employers tried to implement something like this years ago - their "clever" idea was that Jira would record a work log that starts as we used our company id badge to open the gate into the building and then stop the log when we left the building. It's…

Thanks, I think that has cleared up all the bits I was not sure of! So, this library entry is a little bit mis-named - it says "from JQL" but doesn't use any JQL for Server or DC, as it doesn't need to on them. https://library.adaptavist.com/entity/calculate-the-sum-of-fields-from-multiple-issues-from-a-jql-query It is…

I am a bit confused on what you are doing here - how are you trying to read the data from Jira? You've mentioned up to three different possibilities in the question, and I'm not sure what you are actually doing. I grab Jira data in a number of ways: * Through the UI, with a browser. This is the only way the Behaviour…

This is because JQL in Jira Cloud does not allow us to add things like issueFunction into it. So standard JQL can't use it. As you've already found, Scriptrunner's enhanced search does do that. But, I suspect your "api call" is to Jira's search function, not Scriptrunner's enhanced search. so it's failing because…

I think it would need to be a fully-fledged app, I'm not sure you could do everything in a macro. Calls to the API from an external service would also be quite a lot of coding, although, yes, you would be able to construct a small macro that fetches data from the remote storage. However, I think your initial suggestion of…

Where are you stuck? What documentation are you following?

Confluence doesn't have any functions that would do that. You would need to write code that could work out where you are delimiting your sections, then go into the history to look at the last time each section was changed to be displayed (that could be quite hard to write as well, it would have to be able to deal with…

Are you definitely putting the licence key into the "Jira Core" licence box, and not Jira Software or Jira Service Management? Also, what version of Jira Core do you have installed?

That's why I started with "not off the shelf".

Heh, my Einstein result even has my job title in it. (MC = Managing Consultant, right?) You are always the energy and MC to make sure team updates are relative and valuable. You are a master at collaboration, down to a science, not just a theory.

I am sorry, it is not clear what you are looking for here. I understand you're writing a Connect App, and that if you want your client to install it, you understand it needs to go on the marketplace (privately if you want, so only you and the client can install it on your Cloud Confluences and Jiras). But what do you mean…

For the Jira upgrade, start at https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html For Ubuntu, yes, either install a new one, or use the upgrade tools built into your current one to do the distribution upgrades on the current machine.

Jira is not going to be a replacement for a database. Jira is an issue tracker, not a database. If you mean you have been using an access database for issue tracking of some sort, then yes, Jira is good at issue tracking and you will probably be able to import some of your data from the database so you can carry on issue…

Start at https://confluence.atlassian.com/doc/upgrading-confluence-4578.html - the version you are going to is an upgrade, not a patch.

I've only ever seen postgres security done with that file, but it being missing would explain it - the lines in that file tell postgres to let people connect to it. Without rules in that file letting you in, postgres will only let in the local admin user on that machine

Do not try to do this in the database, it is NOT a simple query and you are likely to get it wrong and break your system. You will need to be planning for backups, rollbacks and significant downtime as well.