Nic Brough -Adaptavist- Expert

Ok, so, 1. Migration is not a step that has to use a network. You could, if you wanted to, use removable media to get the data from one place to another. Most people will use a network to do it though, as it is the easiest and usually fastest way to do it. You probably can do this over your VPN, most VPNs support it and…

I think of Jira as having a standard efficiency when it comes to storing files. It does the basics of storage - you give it a file that is X bytes in size and when it stores it, the file takes up X bytes on the disk. Some applications are less efficient, storing the file, copies of it, permanent thumbnails and so-on,…

Yes, if you downloaded it from the Sourcetree site.

Kanban does not have estimates, each card is the estimate. You can put estimates on issues that appear in a Kanban board, add the custom field to the create, edit and view screens and you'll be able to do that. But the board isn't going to look at them.

Good point, it can't be for Cloud, Cloud doesn't support Behaviours yet. I've removed the misleading tags.

No, Advanced Roadmaps does Iayers above Epic. Epic -> Story -> Sub-task remains the Jira Software hierarchy beneath there.

There is a risk, but it's not one that you need to worry about. Atlassian will check for it (they do a pile of checks on the data when they move it from one place to another - same number of rows in every table, identical checksums and so on. Any failure, they will deal with. It is little more than a lift-and-shift though…

I think you're missing the point here - it doesn't matter what the client OS might be able to do, omnifocus is not a registered scheme and hence not a standard, so there's no reason for a service to support it. Not that that matters too much for your purposes, raising the support request is the right thing to do, although…

I suspect there is more to the error than that - what do the logs say? To get this error though, it suggests a damaged Jira installation, or something has gone wrong internally (like out of memory) and it's not able to load some new stuff from the disk.

Jira doesn't have a technical implementation of "product", that's something you have to define and represent in Jira for yourself. Normally we see "product" as "the thing you are building with the help of Jira", but there's no real standard way to represent that in Jira - some people find it best to have a single project…

Yes. If you (or another admin) has allowed them to sign up for an account, or given them one, then yes, they'll have access to your code. My guess is that you'll want to turn off the self-sign-up so they all have to go through your admins.

I don't think it's your "set" code - https://library.adaptavist.com/entity/set-behaviour-hidden is the example I start from when wanting to hide fields I suspect it's the "if" - I don't think the assignee value == "your string" - assignee should really be giving you a user, not a string.

Ok, the details you've given here are a bit sparse, so I can't rule out or talk about several things it might be. Best I can do is to tell you to look at the basic information on an issue that is in the 64 but not the 27, and compare it with the filters. If it does not jump out from that quick look, then what I'd like to…

I would have a look at how you identify the group of people (team?) you want to nominate like this. The obvious way to do it is have a user group that they are all in. You could then add a custom field to Jira - a group picker would then let you choose the team to associate with the issue. There are apps that provide more…

Site admins administrate the Cloud site - the site can be made up of several different systems (one or many Jiras, Confluences, Bitbuckets etc) Administrators should probably be renamed as "application administrators" - they have admin rights in individual systems Site admins can maintain users across the site, including…

There is a technical limit to the number, but it's far higher than the number at which your people will tell you to stop being silly because the board list is unusable and they "can't see the wood for the trees" I'd be looking at a usability limit rather than the technical limits.

Ok, so there's some word usage to clarify here - offline means "not running or not available to use over the network", and online means "usable over the network". They do not accurately describe what I think you are talking about here, I think you mean "on our servers, behind a firewall" when you say "offline", and…

These screens cannot be re-arranged. You would need to make code changes to Jira and you can not do that to Cloud systems.

You'll need to remove their access to the projects they should not be able to see. This means doing things like changing the permission schemes for those projects to stop using things like "any logged in user can browse the project", swapping it to a role or group that your more limited users won't be in.

Welcome to the community! I'm afraid your question is not clear. Your use of the words "online" and "offline" does not tell us what you have or what you are moving to. A Jira system is always "online" - if it were "offline", you wouldn't be able to use it. Do you mean that you have a Data Center install of Jira that you…

Yes, later versions of Jira are a bit more sensitive on what is valid in urls and uris. Omnifocus isn't a registered scheme, so there's no reason to recognise it as "valid" - it is correctly formed as a uri, but not an accepted standard (yet?). That kind of rules it out as a "bug" - the software is behaving as designed,…

Ok, there is nothing in Jira that will do this natively, it has to have been created by an admin with an automation, listener or function of some sort. I'd want to look at the issue history more closely. Exactly what action is the deletion being done by? Edit, transition, or something custom? Might it be an external REST…

No, if you re-organise what you are doing slightly. There is a whole pile of legalese you could wade through, but what it all comes down to is: Each production installation of Jira needs a separate licence But, a production licence for 25+ users gives you access to a development licence key, which you can use for…

Because it's the database that is missing stuff, not the application. Atlassian can't do it, the application needs the database to be reconfigured to support it and the data rebuilt to match the new configurations (restoring from the backup does that rebuild)

Normally Jira will record a field as "cleared" rather than deleted. But that's an aside, probably cosmetic and not helping as an answer. Unless your human is actively blanking out the fields at the same time as editing the content of the user-picker, the only thing here is an automation of some sort that is catching "edit"…

There's no way to increase the limit. I still think it's a really poor design to have too many request types. Think of it from the point of view of the customer. They're trying to tell you "X is broken" or "I want Y". Asking them to select from 87 slightly different request types is a non-starter, you've confused, or…

Ok, that's a long list, and I'd recommend actually just getting stuck in and trying to use it (while referring back to Atlassian's docs on the subjects), but some brief starting answers: 1.Possible to segregate tool for 1 organization having 4 teams? Yes. You can grant access to different projects on a team by team basis…

I would not try to do this, just present the full text to people instead. Atlassian are doing the right thing in gradually removing the ability to inject dubious javascript into fields like that, so even if you could get it right, it's going to stop working soon.

What do you mean by "fields get removed"? The data in them is deleted? Or they vanish from the screen when you change the user selected (if that, then do they come back if you reselect the old user)?

I like @Dave LIAO point about time. I'm a night-owl but some of my team are morning-larks. We can't change that, but being aware of it means we can be more productive together if we plan the closer working to fall between 10am and 4pm But I wanted to talk a bit more about something @Christine P. Dela Rosa mentioned - types…