Nic Brough -Adaptavist- Expert

The guide is up to date and works fine - one of my collegues was using it yesterday. What error are you getting?

I think you're really going to struggle with this one. Sub-tasks are not independent items outside their parent story, they are very much a part of a story. A story should be worked on by one team, not several. Sub-tasks are there for breaking up stories into smaller parts so you can assign different team members, or use…

Yes, I have totally misunderstood the question. It appeared to be a problem with rendering email that Jira was sending to me. Re-reading it as incoming mail, my answer changes a lot: Jira is taking the content of your emails and trying to render them as best it can from the content, but your emails appear to have call outs…

Parentheses are always your friend with multi-clause JQL, but they don't do anything when you're only using AND. Project = (project name) AND issuetype = Feature AND Status= Funnel and Issuetype = story and status = In Progress This will find issues where * Project = X * issue type is feature * issue type is story * status…

You do not. Workflows do not contain issues. Workflows are the technical definition of the steps (status) that an issue may go through during its lifecycle. Projects contain issues, and workflows are independent configuration items that exist independently of projects (you then confugre projects and issue types to use the…

There is no simple estimate. You will need to decide what you want to run with and run it through some calculations. Start at https://confluence.atlassian.com/enterprise/node-sizing-overview-for-atlassian-data-center-941612709.html to think about how to size your nodes, and then…

I am not sure that the user management tracks that. If it does though, this is something you will need to take up with Atlassian support. We community members have no access to your systems. Raise a support call at https://support.atlassian.com/contact

I do not understand that question.

It looks like you have swapped from working in Jira to working in your Atlassian site maintenance. They're different systems with different menus. Try going back to your Jira and hit the settings menu again.

There are broadly three things this could be: * You have got an incompatible version of the app for your version of Confluence * You have some incompatible data in your database that the plugin cannot work with (this could be corruption or possibly data created by another plugin, although in this case the error seems to be…

A filter returns a list of issues that match criteria. The list is de-duplicated in the cases where an issue is selected more than once (if for example I search for "Pet = Cat OR Legs = 4", then my cat would be selected twice because she's a cat and then again because she's got 4 legs). So I am a bit lost on what you are…

The "may have been deleted" message is shown when you try to directly hit an issue that has been either deleted or hidden from you. I would check: Can you see the project the issue should be in? (If you can see other issues in the project, that's a yes) Does the project have an "issue security scheme" set If it does have a…

The migration assistant needs to use your Jira to read data out and push it into the Cloud Jira. This does mean your Jira needs to be internet accessible, yes.

Thank you @Susanne Götz _Tempo_ for saving me have to look up the tables, and explaining it better than I could!

There is no "archive", if you remove an issue type from a project, you have to tell all the issues currently using it to become a different type. So, yes, if you want to remove an issue type from a project without changing the issues that are of that type to another, you have to move them to another project that retains…

The background to this is that the .bin file is an installer, intended to be run by your operating system, to install or upgrade one of the application bundles (Core, Core + Software or Core + Service Management) from scratch, creating a new or upgraded service. The .obr that Dirk refers to is just the application or app,…

The "licences" are per system, not by user, so yes, you're using two different systems, so you need to pay for each. Imagine it as if Confluence 1 has a licence for 50 users and Confluence 2 has a licence for 100. You get access to both via an account, each access counts towards the consumption.

SQL is a terribe way to try to report on Jira data, the database is almost as far away as it can be set up for reporting and most of the queries you'll want to make are torturous and slow, as well as, in some cases, simply not there. Some of the stuff you see on screen is not in the database at all. Ignoring that and…

Not an open one, no. It's still a very simple response of "stop using different fields for the same thing"

But what types of field are each of those? And what type of field is developed by?

Please see the accepted answer, it's the only way to structure a secured space.

If you can't select or mention a particular user, it probably means that they cannot see the issue you are working on, or they have been removed from Jira.

In Jira, fields belong to issues, issues do not belong to fields. The Date and Date/Time fields that Jira provides only hold single dates at present. What data are you trying to capture here? There may be a way to do it without needing a new calendaring solution.

I'm afraid a project can only be in one category at a time. You might want to look at the "profields" app, which can add fields at a project level though. That might help you with categorisation of projects too.

@Thomas Bowskill- definitely extending and adding more info. Thank you for chipping in!

Do you mean transition or step? These are two totally different things.

You're trying to do something that draft workflows do not allow. This is likely to be deleting a step or status or adding a transition to a step that does not have any outgoing transitions already.

If you go for read-write on the Jira side, then they'll be able to do it from their profile. What it looks like is an "old password, new password, repeat new password" set of questions on a screen.

You don't do this on Cloud. I am going to guess you got the question about Cloud and Server wrong, and you mean Server. You only need a new licence if * The new server is a new server and you are going to carry on using the old one. If the new one is a replacement for an old production system, you don't need a new licence.…

A lot of this depends on how you are recording work and how you define a project as "done". Jira is focussed on the issue tracking and tends to build reporting from issues. Projects themselves are not the prime artifacts, so generally you'd need to build this from looking at issue statistics of some form. Start from how…