Nic Brough -Adaptavist- Expert

Links in Jira are directional, they indicate the direction of the relationship. If you choose "causes", you'll find the system displays the two issues at each end as "A Causes B" and "B is caused by A". They do not do anything more than express a directional relation without additional config and coding.

We often find long complex lists of portals and request types - don't do this to your people. If you genuinely need to after you've had a think about why your people are picking the wrong things, then look into re-wording them to make them clearer.

Unless the vendor specifically documents it, there's not a lot of hope of doing this. They might have done one of the nicer options to be nice to our admins and you might find something like "adding resolution" in the application log at start-up, or possibly lines in the admin audit log. They might not even be doing it on…

Locked fields are locked by the plugins or core code that needs to protect them from potentially inappropriate change or deletion. Unless Atlassian documentation explicitly says "you need to unlock this field", you should not unlock them. Some of them probably could be deleted safely, but most will break things if you were…

Go into the admin bit of your Jira Software, find "manage applications" and you'll be able to add Jira Service Desk there. It should tell you which is the latest version available for your current version of Jira Core (If not, then have a look at…

First, decide on a target. Latest Jira Server is 8.6 (Enterprise, with long term support is 8.5). Or you might be looking to Cloud instead. For the server upgrade, see https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html You'll need to do that anyway if you want to move to Cloud, as…

No. Because most of the functionality is in the code, not the data.

No. Because it is illegal. Pay for the licences you are using. Or at least will be when you've finished cleaning. It would also take longer to write an automation than it would be to complete your cleansing process, after which you don't need to do it anyway.

Yes, that looks correct to me. You seem to have put the attachments macro on the same page twice. As it lists attachments on the page, I'd expect to see what you are seeing there.

There's a trick to this. The parent ID in your CSV file is not the Jira parent id, it is a simple convenience for tying sub-tasks to parents. It won't actually be imported. You must be careful with the order. Make sure your parent issues are higher in the file than their children. So, let's say you have a really basic…

Absolutely not. You are breaching the terms of service on your licence agreement. If you need more users, you should buy the service for them.

Does the account logging in to run the python have "browse project" permission for all the projects it should see?

No, you cannot duplicate IDs. Even the code can't do it, one of the few database functions Jira does use is to prevent duplicate IDs.

It is possible - broadly, Jira 6 through to 8 have compatible-enough REST APIs that you won't see many problems with them, especially if you're only doing the basics of linking issues together. Question though, is there a reason why you've not installed Service Desk on the existing Jira Software? No need to link,…

You click create linked issue and answer the questions it asks. See https://confluence.atlassian.com/servicedeskcloud/blog/2016/02/create-linked-issue I don't understand the question about "operation change", but if you mean you are expecting to go back to where you clicked the link from, yes, you go back to the issue view…

Your LDAP connection settings are broken, and it can't connect to it to get the user lists. See https://confluence.atlassian.com/confkb/lexical-error-during-directory-synchronization-271942578.html

The main pro is that people find it incredibly useful to be able to label and then search and report on free-format labels that suit themselves. The downside is people can't type, or try to be clever and you end up with a lot of singleton, or meaningless labels. You will always find some people overdo them (labelling an…

WE don't know. What do you mean by "badge upload form"? It's not a phrase I recognise in Jira

No, you have not. You have added "summary 100" to the screen. You need to add "summary" to it, not an arbitrary custom field.

You can try to do this without additional apps, but it won't work too brilliantly. Most people attempting this instinctively model test cases and plans as issues in projects. The problem with this is that issues are workflow models, not re-usable plans. They're expected to go through their workflow once and then get shut…

Apps for Server and Cloud are very very different beasts, you won't get a lot of sharing done (unless your tactic is to run a remote service like Cloud Apps and work exclusively remotely). You'll also find that the Cloud and Server REST APIs are not identical because the products are diverging.

Cascading select lists are part of the core product of Jira.

There is an emergency backup for re-creating swathes of Cloud systems in the case of a wholesale failure. But it's not suitable for recovering a single system I'm afraid if you have no backup, there's nothing you can do, your data is gone.

We don't do that - people are often active in several different projects and our reporting covers that automatically. We don't use this stuff for planning much, as the nature of the work for a lot of us means itis not that helpful. It sounds like you do need a strong link into a project, so it may well make good sense to…

Ok, flip my "reporter" over to "assignee". REST is fine, you can run JQL over it and get a block of json with all the issue data in it

Yes, you are looking for a field of type "cascading select". Our usual example is "country / city" but the words are not important.

Yes, you could do that. I left out sub-tasks as a potential confuser, but we do actually use them in the scheme I'm thinking of. Although we have our issues outside the projects in a container for "not work" (and we need a bit of security as the visibility of some of our not-work stuff is sensitive, so we need a security…

You can run JQL over rest - "sprint = 232 and reporter = user" should fetch it (I'm not sure what you meant by "by a user" so I took a guess at it being the reporter)

Oh gods, wrong time to ask. I'm on a course this week with 20 other expert Jira admins. The instructor found a really odd thing in the data as we started one of the exercises, and almost broke down and wept when he say a mapping for multiple-assignee with a jira custom field. The entire room sympathised - we've all got…

I'd start at https://www.atlassian.com/trust/security but if you want to get stuck right in, I rather prefer https://confluence.atlassian.com/cloud/follow-cloud-security-best-practices-962980119.html There's also a nice little index at…