Nic Brough -Adaptavist- Expert

There is no concept as a "sub-board" in Jira, you simply have boards. Boards are a view of a selection of issues, they're not containers for issues. You do not create an issue for or on a board, you create an issue and it will appear on boards that select for it. The project type matters in the next bit of the question -…

There is no soap web service in Jira 8. If it's just updating issues in Jira locally on create, I'm very confused on why you are asking about the soap service?

Jira rightly only has a single assignee, as the person currently responsible for dealing with the issue. You can add other people as interested with watchers, assigned sub-tasks, group selection fields, user-pickers and so-on, there's plenty of ways of including others.

For an unmanaged one, yes, just change the email address - that way you get to keep everything you had associated with the account (even though your company are probably going to remove you from their systems). Stuff like your kudos and badges here belong to your Atlassian account. It's also a lot easier than delete and…

There might be, it depends on how you want to record it. Could you explain how you are tracking the time attendance and what the shape of the data is that this gives you?

So what version of Jira are you on? Only very old (certainly out of support) versions have a SOAP API. To get Jira to talk to over systems by making SOAP based calls to them, you're probably going to need to look at coding. What calls does the other system require from Jira?

Ok, that's a merge. not a migration (semantics, I know). Have a look at the Jira Cloud migration assistant, it can help you move bits of one Jira into another Cloud instance and works with both Cloud and Server sources. If that's not going to cover what you need, then I strongly recommend what @Prince Nyeche - ELFAPP has…

I am sorry, but you have landed in the wrong place. Minecraft uses Atlassian software to support its systems. You have clicked on "help with Jira" instead of "help with Minecraft". We here cannot help you, you need to talk to Minecraft. ----- 抱歉，您落在了錯誤的地方。 Minecraft使用Atlassian軟件來支持其係統。 您單擊了“ Jira幫助”，而不是“ Minecraft幫助”。…

You will need to find a way to add conditions to the workflows (the ones built into Jira off-the-shelf are not very configurable when it comes to custom-fields) Once you've got a method for creating conditions, edit your workflow - you 'll need to create all the different transitions you want to allow depending on the…

How are you recording "time attendance" separately?

This will happen if you create a project that you do not have permission to see. Go back into administration (admins can always see all the project;s administration sections, even if they are not set up to see the project content!), you'll be able to find a link to the admin section of your new project, go into it and…

There's two things you might be talking of here, probably easiest to think of them as "incoming" and "outgoing" relative to Jira. SOAP is a method Jira used to have to enable "incoming" - meaning another system wants to talk to Jira, it pokes it over the SOAP API to ask Jira questions or give it commends. SOAP was…

When you say "migrate", do you mean "merge one Jira Cloud system into another one, move your people over to the target (and probably stop using the source instance"? Or something else?

Oh wow, you've hit on something my family has always encouraged members to give a go, and I'm not sure which thing on the list is most unique. I have: * Driven a commuter train into London * Driven a steam train * Flown a passenger helicopter (that thing where an air pilot lets a kid take the pilot's seat and hold the…

Yes, those are correct, but I wanted to point out that security levels are not based entirely on groups - you can use roles, individuals and fields in them as well if you want.

To transition back, the workflow has to implement a transition in the opposite direction. You'll need your admins to edit the workflow and add the transitions.

You don't need to remove inactive users to stop them counting towards your licence count, just disable them. What do you mean by "can't add new users"? What is stopping you?

The issues in your screenshot are all in status that do not have a transition to delivery backlog, or to analysis. You'll need to transition them to DVF, then the transition to delivery backlog will become available.

The docs say to use the Xray test case importer, not the Jira issue importer. See https://docs.getxray.app/display/XRAYCLOUD/Importing+Tests+using+Test+Case+Importer

You should start by not assuming everyone knows what your random unexplained acronym is. First hits on search engines are an airport and a church, so all I can really answer is "how is your airport using Jira?"

There's no way to restrict this. There's also no good reason to do it, if people have an interest in a workload report, then they can always create one from the raw data (which has a chance of them getting the calculations wrong). Why do you think you want to restrict it?

You'll need to fix your Linux install, it sounds like it does not have access to a valid yum repository Try running (as a superuser) "yum install fontconfig" to get an error message that should tell you more about the problem.

The exact setup is not relevant because there were many differing factors. There were several versions of linux installs, several variants of the JdK 11 and several off-the-shelf installations of Jira and Confluence (mostly the long-term-support releases) that had problems. All reported to the relevant vendors. Some were…

Several versions of Jira 8.x off-the-shelf, several JDKs, and an assortment of Linux kernels (we've also seen problems on Windows, but as no-one in their right mind uses Windows, we fixed a lot of stuff by switching people over to a proper operating system)

I'm not sure there's a lot more to add. Install Jira or Conflluence on a server that has JDK11 on it. Test them. Things do not work. Install JDK8 and set the systems to use that, and the things that failed on JDK11 work fine. Literally - one JDK verstion fails, the other does not. I don't think it matters exactly which…

In Jira, "move issue" means changing the project or issue type (or both) If you wish to re-rank or put due-dates on issues, you need the schedule permission. You also need the edit permission if you wish to change data on issues. The rank is data on an issue, so to rank stuff, you need edit prmission as well as schedule.

1. No The issue creator can set a priority. As I said before, the set-security only affects the security level 2. No, as per 1. 3. If an issue has a security level, only some people can see it. Those who can see it can do whatever the rest of ythe permision sheme says they can.

Just to remind people to test - a number of us have seen problems with JDK11 deployments. It's completely subjective (hence the comment about testing - it will probably work, but you should never just jump to a new thing just because it might be better. Test that jump), but Jira on JDK11 failed us on work logs, both…

I am not seeing what you are. How our you "adding workflows to workflows" and "linking status to status"? Neither Cloud nor Server Jiras are offerning me that!

Frankly, nor am I. I have been here a while, so I've picked up some of the names to ask for some problems, but not this one. I'm sure someone will see us soon (fwiw, my label flag is not the only "escalation"(