Nic Brough -Adaptavist- Expert

It's across the scale too - we've got a an admin and migration helper app that throws out a few reports that can save you a lot of time when housekeeping or thinking of migrating a server system to somewhere. It's $10 for 25 users. It's $10 for 10,000 users. It's totally aimed at your admin team, only they can run it (and…

I'm afraid you need to go back to your customer and tell them their "requirement" is, well, to be diplomatic "non functional". It's simply going to break everything and they should not do it. Tell them that the better options are to stop doing sprints and adopt a queue-like system. Scrum is not right for them, obviously.

Welcome to the Atlassian Community! No, but yes (ish). The licences each organisation has only entitle people to use the Jira that belongs to that organisation. Think of it this way - I have access to Adaptavist's Jira because they've granted me an account on it. This does not entitle me to use anyone else's Jira, it's…

That suggests that you might have damaged your database with SQL, or you are entering a URL that is not running a Jira, or you can't reach it from this server.

No, it should be fine. A regular re-index shouldn't be necessary, I prefer to leave it to the admins to decide when one is needed and let them kick it off.

Just to be clear, this is absolutely not the case. Jira and Confluence index individual items whenever they are changed. If you are finding you need to re-index more frequently than every month, you've got significant problems and you need to investigate and fix them.

What do you mean by "cleanup queries"? I'm scared that you might be destroying your Jira system by writing to the database... The short answer here is that you need to put in a valid base URL for the Jira system 

Yes, the way the database is used as a data store, and the logic done in the application means that you're never going to be able to write sane, performant, SQL that is of any use for reporting in all but the most simple of cases. If this is to go into Grafana, I'd go a different route, one of * Write a proper extractor…

Your test case imports are probably a function of a test management app. Core Jira has CSV imports as the standard way to bulk import issues (and they can import bulk edits as well) See https://confluence.atlassian.com/adminjiraserver/importing-data-from-csv-938847533.html

There's a trick here - radio-buttons and check-boxes are just different representations of single-select and multi-select lists. All four are select lists in the database, so the code for reading and setting them is the same! I find this a useful bookmark…

Welcome to the Atlassian Community! No, there's nothing removed from Confluence. The video is an advert for an app that adds bulk delete to Confluence.

The issue views in Company managed projects are very different to tam-managed. They are mainly determined by their "screens", which are lists of issues that should appear in the four cases (create, edit, view and transition). The view screen is fixed, there's no choice in where fields appear, other than their order in the…

There's no easy way to work this out because the keys that belong to other accounts should not be shared, so it's not easy to search. If you shared the key with someone, you should know who. If you were given the key by someone, then you'll need to ask them. If you have no luck chasing it down, you can raise a support…

Welcome to the Atlassian Community! What Python libraries are you using to make the REST calls to Jira for the data?

Welcome to the Atlassian Community! Fields are defined as "read only" by virtue of being a read-only field (there is a type of field for that) or by not being on screens where people can edit them. A listener has nothing to do with the configuration of a field, it's there to take action when events happen. You could write…

This looks like you've created an application link to their Jira and after upgrade, it's asking for re-authentication to check it is allowed to connect to the new system. It does not look like an app has been installed (but if it has, then it was an app that was installed before you upgraded, it's not self-installed, it…

Welcome to the Atlassian Community! This can only be done if the app you've installed supports project-by-project permissions (most do not, it's quite hard to do it in Cloud)

The installer does all the work automatically. For a simple non-customised Jira install, the installer can do everything except click "update" on all the apps you have installed. The manual upgrade needs you to do all the work of installing from a pile of files, so there's a load of files to edit and get right. But it does…

My fault just as much as yours! We can't know when someone else is going to post! Yes, that's a good way to do it. Issue link types are stored in a database table that looks like this on a mostly untouched new Jira, so my guess is that you'll see the entry in the linkname column…

It might, but I cannot remember. Sub-tasks are partially stored as an issue link type, one that is hidden from the UI. I can't remember if the API is clever enough to ignore them when you use that code. I'd recommend ignoring them in your script though, you need to do some extra stuff in other places if you're changing…

Ah, cross commenting. Yes, that would damage the sub-task relationships - part (not all) of it is stored as (an invisible) issue llink.

The only way to do that is with code that removes the parent issue, forcibly, overriding the relationship that Jira enforces. It is also possible to hide the relationship, which makes them look orphaned, but you can't do that in the workflow, you have to change the parent's issue type!

No, they're not considered to be issue links. In the background, sub-tasks and issue-links have a lot in common, but because sub-tasks are a fragment of an issue and links show a non-hierarchical relationship between two issues, they look and behave very differently.

No, it's not possible to do this. You can only restrict issue visibility by using security levels. You could set up something convoluted about setting security levels with Automation, based on other fields, but it is complex and unwieldy, and the complexity usually means mistakes will happen and people will get to see the…

Welcome to the Atlassian Community! This suggests an automation or script (post function or listener) that is deleting or changing the parent of the sub-tasks such that they disappear from the parent issue. Check with your admins what they have set up in the project, or listeners.

I'm glad to say that Cloud does not allow you any access to the database. This is a good thing because SQL is the single worst possible way to do any reporting on Jira. You will need to rebuild your reports using sensible methods of reading the data. Ideally look at adding reporting apps to your Cloud system, but if you…

Have two field configuration schemes, one with the field flagged "hidden", the other with it available. Use the hidden one for most of your projects, and the other for the project the field should appear in.

Jira is a field based system, not a free text one. As I've already explained, click to edit blocks the other useful functions that puts Confluence ahead of its competition and makes it easier to use both as an author and reader. Yes, you need a save button in order to confirm that you have finished editing and want to…

Have a look at the time tracking reports and the gadgets you can put on dashboards that report on user activity. For something a bit more powerful, look at the planning and timesheet apps you can get from the marketplace.

To get in touch with Atlassian, raise a request - start at https://support.atlassian.com/contact What do you need to ask them though? We might be able to help.