Nic Brough -Adaptavist- Expert

You can enter a field description in the field configuration scheme, or under the field's global configuration.

Ok, that answers it - TMPs only have a single sub-task type.

My guess would be that your user does not have the permission to assign issues. If they do not, the field will not be offered to them for entry on create or edit!

Welcome to the Atlassian Community! Advanced Roadmaps is part of the premium subscription, it cannot be installed as an app. You might want to look through the marketplace for cheaper apps (I'm rather fond of Big Picture for doing reports like AR does, and Structure for giving you many layers of issue types over…

Welcome to the Atlassian Community! You can probably do this with an automation, but you'll need to look at whether you mean resolution OR status , or both. ("resolution status" does not exist in Jira, they're two independent things)

This is how it is supposed to work, when you have a backlog enabled - new issues should go into the backlog, to be moved on to the board when the team decides it should. The most simple test you can do is to re-configure the project, turning off the backlog option (this test will not affect any of your issues when you turn…

You can't get trial licences for Server any more, they were deprecated a couple of years ago, as Atlassian are going to completely drop Server next February. So, this means your licence probably covers an older set of versions. You can only use a version of Jira that was released before the end of the licence. As your…

Templates can't be nested, when you create a page, you have to select a single template.

Welcome to the Atlassian Community! This looks like you have taken a backup of one Cloud system and are trying to restore it into another. This process can fail with "out of date" errors when the two Cloud systems are on different builds (It takes weeks for Atlassian to roll out the latest version to everyone). I would…

What error message are you getting? Assuming it is "can't do this on a draft workflow", then the answer is that you'll have to take a copy of the workflow, edit the copy, then replace the association in the workflow scheme.

Welcome to the Atlassian Community! Jira does support sub-task estimates, if you look at the "sigma" fields, you'll find they are an accumulation of estimates and work on issue and its sub-tasks. It does not support the non-scrum practice of putting sprint estimates on sub-tasks because that's not what Scrum or Kanaban do…

Welcome to the Atlassian Community! I am sorry that the answer you got before was misleading - it was generated by an AI that has no understanding of your question or Atlassian software. It's not a complex process, but there are some things you may need to think about. The best way to do this is to search for the issues…

Welcome to the Atlassian Community! With no changes to dbconfig, that suggests your database has had the credentials changed, or a network change has blocked your server's connection to the database.

The error message you are getting here is self-explanatory. The issue types in your project are configured differently, so if you want to change an issue to another type, you need to go through the validity checks and migrate it, correcting any missing required data and accepting data loss from fields. Bascially, click…

You need one of your billing contacts to click on "payment details" and correct them so that the bill can get paid.

You can also do it without opening an issue, if you use "bulk edit" in the issue navigator (search results)

It is not clear what you are trying to do here. Could you explain "able to see some message" more please?

Welcome to the Atlassian Community! Sub-tasks are not useful in backlogs, so you won't get to see them in this structure (you don't estimate them, you don't bring them into a sprint, nor can they be ranked outside the issues of which they are a part) But you can get to see them in a backlog - add the "sub-tasks" field into…

Welcome to the Atlassian Community! There's a lot to talk about here, but I'll try not to write an essay. * Story points are not a time estimate * If you want to be estimating in time, the best option in Jira is to use the time estimate (original estimate, remaining estimate, time logged, etc) * Sub-tasks are not…

If you block the port, the service can't be reached by other systems. What are you actually trying to achieve here?

Story points are an estimation tool, not a progress measurement. There is nothing to "fix" here, Jira handles story points as estimates, as it should do.

Ack, sorry, I was looking at Jira questions at the time I answered. The doc I linked to still stands - it's got the Confluence end-of-support dates in it as well as Jira, and yes, you're out of support in a couple of weeks - you'll need to upgrade or migrate (off server, so that you remain supported after next February)

Welcome to the Atlassian Community! Your third point is the one that matters - the issues must be in the last column on the board that the sprint is defined for (it won't work if it's another board with a different "done" column"). Do your issues have any sub-tasks that are not also shown in the last column of the board?

Then you have either not associated the issue type scheme with the new sub-task to the project, or it is a team-managed project (which don't have issue type schemes, just a tick-box for enabling the single sub-task type)

Welcome to the Atlassian Community! Atlassian are not going to change their current policy of licencing apps for everyone who may use them.

You can't swap the domain of an Atlassian cloud system to one that is already in use, you would have to merge the systems to get them to run on the same domain, or destroy the existing one if you no longer need it.

You can change the site name later, if you set up a temporary unique string for your new site.

Welcome to the Atlassian Community! Jira 7.13 is already out of support - the oldest version currently supported is 8.19. See https://confluence.atlassian.com/support/atlassian-support-end-of-life-policy-201851003.html Also, all support for server ceases on 15/2/2024, no matter what version it is. Only DC and Cloud will be…

Every report of potential junk is useful. Thank you for the report, our moderators appreciate it more than most think! (Someone got to it before I could, and removed it!)

DC and Cloud have the same access model - you give people access to your systems as you need them to, and you allow/block IP addresses as needed. The allow/block works a bit differently - with a server/DC system, your network admins are totally in charge, but with Atlassian Cloud, you need to be looking at the white/black…