Nic Brough -Adaptavist- Expert

You can't "assign a workflow to a board". Workflows are determined by the issue type. An issue will follow a single workflow through the process, the board and person looking at it can't change the process it is using. For your two boards, you would have to use different issue types (or projects) to do it. To move on to…

Workflows are determined by issue type, not board, team or type of person using Jira. To use different workflows, look to the project's "workflow scheme" - this tells the project which workflow to use for each issue type in the project (and has at a minimum a "default" to use for all issue types that you do not define in…

Space imports from versions below 6.13 can work if you have not done anything too clever in a space. But your only other route is to create a temporary development server on a version that's high enough to run JCMA or do the imports, while low enough that moving from 5.7 is an easy task. Either take a copy of your current…

It's a quirk of logic that humans find counter-intuitive, but when a multi-select field has nothing to work with when you say "field has X", it does not match. Null is not something you can compare with a value. When you say "component in PBE", that clause ignores all empty components, because there is nothing for it to…

I'm afraid your best option at the moment is to document it for each client and get your users to look it up for each one when they need to know. I'd also go through https://support.atlassian.com/contact to raise an improvement.

The logs won't tell us a lot more. You need to connect a new Jira installation to an empty database, not one with data in it, as the on-screen message says.

What bug? You don't need to be an admin to comment on a card. I think you might want to take a closer look at your site settings, as it sounds like one of your admins has got something very wrong if your members can't comment.

Confluence doesn't have "stable" versions, it has versions that are released because they work. On top of that, the problem here is "This applies to applications that allow untrusted users to upload/modify velocity templates" Confluence doesn't do that. It's code change (requiring root access to your Confluence server), or…

You'll need to enable the initiative issue type and add one or more of them to a project's issue type scheme.

You can't say what template a project is using - they don't use them after creation! A template is a thing used to create a new item, which then goes its own way, the template has no relationship with the new item after it has been used to create it. The differences between templates are in the fields, screens, issue…

You'll need to ask Atlassian to do that. See what @Felipe Kraemer said!

Yes, you can customise any workflow in Jira to match all sorts of processes. But Epics are supposed to be a natural grouping of stories together and tend not to need it (or other Epic types). Software like Align, Advanced Roadmaps, BigPicture and Structure can give you more ways to work with Epics though.

Have you added the type to the project's issue type scheme?

The sort order in your sprint should be simple "order by rank", you can't do drag and drop if issues are not sorted by rank alone. However, your initial question was right on the very first line. The sort only considers the first three items in the order by clause!

Custom fields don't have the functionality of the priority field, so I'm afraid you don't get the colours and icons that priority supports.

I can talk about years of using it with different places!

Go to the page and look for the restrictions icon (small red padlock) - this lets you set individual page restrictions, but also explains the inheritance of the current restrictions on it.

Well if you can connect from somewhere else with the same credentials, it must be the mail server! I'm not a mail server expert, I know just enough to make one of mine work, and I don't know if it's the same as the one I know a little about. There are two places to look though Linux machines almost always have a firewall…

You're right in that this shouldn't work like this - if you're not at the security level, you should not see the issue anywhere. I too want to ask for the info @John Funk asked for, but could you also tell us the issue types? I'd like to rule out dubious practice with sub-tasks that can be set up to break security in the…

It's got a small step further: People on the more expensive options than "free" and "starter" can now edit their own <something>.atlassian.net in their site Admin settings. But it still has to be <something>.atlassian.net Atlassian has said Cloud-6999 is now targetted for Q2 2023, but with incremental changes happening as…

Yep, all your options are things you can choose to do later!

There is a request somewhere, but it's not one I'm watching or bookmarked. I'm usually the admin, so I can go look it up and get asked to explain it too. There is a cheap trick for end-users - edit an issue or worklog repeatedly until you get a match. Change the entry to 5h, look at the issue again, change it to 6h, look…

Pizza last week :-) This week, we may be out for one of our friends celebrating finalising getting her new house! If not, then it will probably be me setting fire to a salad again...

There is a slightly odd way the Epics have been implemented here (it's a historical quirk from when Epics were first added to Jira, one Atlassian never refactored out) * Epic Name is a field that names an Epic * Epic Link is a field that links an issue to an Epic * They are intertwined, so they provide the issue/Epic…

Repeating the spec does not answer the question. Could you please explain what problem doing this would solve? Why are you trying to display something the users have no use for in the screen? How would seeing it help them do their work and update the issue? As for how, I've already told you that above. I'm just trying to…

Yet again, you can't do it on "create issue" because you don't have the id yet. And could you please tell us why you want it on a transition screen? What does it tell the user that they need to know when they're transitioning the issue?

An issue will not have a key until it has been created. You can't put something on the create screen to show the key because you don't have one until after you've created it. Also, why do you want to see the key as an issue transitions? What does it tell the user who has already read the issue and decided to move it to a…

No, view restrictions cascade down from the parent pages.

You're going to need to explain this a bit more. My Sourcetree is working fine with Github 2FA, so there appears to be nothing to fix. What have you set up differently to me? Could you explain what you have set up, what is going wrong, and what change you made that stopped it working?

Advanced Roadmaps automatically shows the hierarchy in plans, but there's not general display of the hierarchy (mostly because you can't change it, it's not a configurable thing, it's always intitiative -> Epic -> Issue -> sub-task)