Nic Brough -Adaptavist- Expert

There's no function for moving or copying one custom field to another in Jira beyond the manual editing, bulk-editing or using an automation (which would require you to update every issue to trigger it). I would be looking to a scripted solution for this - an external script that can read the issues and update them over…

JQL doesn't have a "count options" or "size" function built in, so you'll have to use an app to provide one. Joseph has given you one very good way to do it, but you could also use Scriptrunner to create a JQL function that can look at the number of options in a field on an issue. I slightly prefer the scripted field…

Cloud has a couple of apps installed as part of the standard offering, one of them provides "update custom field". But Server does not include them automatically, so you'll need to find and add one. Scriptrunner is a good option (I would say that, I work for Adaptavist), but there are several which provide "update custom…

Scriptrunner is an app you can add to your system - go to Admin -> manage apps and you'll be able to search and add it. One of the functions it provides is a "script console" where you can write and execute code, so you could write something in there to iterate over your projects and add people to a role. And just to be…

Mmm, a filter should simply return a list of issues to whatever is asking to run the filter. A gadget shouldn't be any different - most of them do say "hey, filter, show me what you got" and then process the list of issues into a display of some form. Could you tell us a bit more about the problem with the gadget? I mean a…

This is what it says on the tin. (Edit - sorry, I should have said this originally, but got stuck into the answer instead and forgot). But it's not a well-labelled tin. The error is short, as they should be, but doesn't really tell you what it actually is, let alone why it's that way or how to fix it! When you raise a…

That completely misses the point of doing Scrum estimates. It's not the wrong thing to do, if it suits you, but all I'd advise there is acknowledging that you're no longer doing Scrum and hence there are some things in the Scrum tool (Jira Software) that are not going to be useful to you any more.

You don't. Jira does not do sub-tasks of sub-tasks. There are however, some apps that add something that looks a lot like it. The go-to app for me on this is Structure.

It's not specific to Confluence Cloud admins, but when someone asks you for something, default to "no". That's harsh, but you are the one who is going to have to clean up any mess people make, and part of your job is probably to be thinking about content, ease of use and looking after the platform. Always temper that "no"…

Yep, people don't like "enter everything only to be told I can't and have to start again with a different type" Of course, my training is screaming "don't try to limit your team like that, they're supposed to actually know what the right thing to do is", but you could separate out the Epics by putting them into a different…

I've not seen one specifically for SysML, but as it is a sub-set of UML, I think the UML apps might be worth a look. https://marketplace.atlassian.com/search?hosting=cloud&query=uml (I've had some success with the PlantUML app in the past, but it would be unfair to only point at that single option, there's others that…

On the second part of the question, no, there are a fixed set of project types you can create in Jira. These are determined by the code, and they refer purely to the Jira application that generates them. The names are derived from the name of the group of Jira functionality that the projects are going to be using, not…

I'm quite fond of the apps that move your reporting back into Jira and Confluence (I've spent years having to explain just why the "build your own report" business reporting tools have a nasty tendency to generate reports that are, well, wrong), with gadgets and reports. But if you can't do it that way, the first option I…

I can't quite separate myself from the core of my VHS collection - Every episode of Doctor Who from Pertwee through to McCoy (plus the McGann film and a pile of Hartnell/Troughton stories too) and a complete set of Blake's 7.

You don't need to. When you add a project role, it becomes available in all the projects immediately. Do you mean you want to add users to the new role?

 I was using "customer" in the sense of Jira account type. These potential customers need access to your service desk so they can open requests for questions, get responses and so-on. Which is exactly the same as your real customers usage. So you might as well add them as (Jira SD) customers, and remove them when you don't…

Ok, but why would they not be customers at this point? They need the same access as customers as you describe it.

Yes, add them as customers, then remove them when you don't need them any more. I think there's a deeper use-case than you've described here though. Could you expand on that? My answer only caters for what you've asked, and I think there's more to it.

Actually, it does. From To-do, you can go to in-progress. From in-progress, you can go to done. The diagram it generates might not be clear, but reading through the transitions tells us that you do have a To-do -> In-Progres -> Done path. You have extra transitions though - to-do straight to done (not a problem, useful for…

The original directories fall out of use in DC, so you don't need them. Obviously, keep a backup for a while, but you won't cause any problems if you just move them out to somewhere else to keep for a few weeks.

You'll probably come back to https://docs.atlassian.com/software/jira/docs/api/REST/1000.824.0/ quite quickly while you're investigating this, it has all the core calls you'll need and some examples with them. There are some useful getting-started links in the first couple of sections of this guide though, which is why I…

What data on the issue determines which board it should be selected by?

Go into edit mode on the workflow and click "add transition". It'll ask you for the start and end point. Once you've added it and saved it, you'll be able to use it. In this case you probably want to add To-do -> In progress, and in progress -> done

Go to Admin -> Project roles and add a new role. This will immediately become available in all projects. To add people to it, you'll need to visit each project's user admin page

There is no single object export for Jira, not to a format that can be re-imported later. And the on-screen exports (Word, XML) don't include subtasks. You'll need to write something that can grab an issue and it's subtasks, save it in some format (JSON is what I'd reach for too, as that's what the REST API works with…

On the apache server, change the site-enabled that serves up the site at tbjira:8080 and tell it to use the new Jira url instead.

They will need to change the "field configuration" for the project and issue type, or the validators in the workflow (those are the two main ways to make a field "mandatory")

You will need to find or write an app for Jira that can go read your "admin" system for details to be displayed. Obviously, your admin application will need to hold a user mapping (unless it's using the same user directory Jira is already) to enable it to look up a Jira user.

The REST API does not yet expose any form of user activity tracking. The best you can do is look for issues that have been updated by someone and read their histories and comments.

There are some things you can change, but not a lot. The config is in the settings menu on the page you are viewing.