Nic Brough -Adaptavist- Expert

Yes. Remaining estimate is nonsense on a burn up chart, so Jira does not bother to offer it.

You can't, the list is hard-coded for valid sprint estimate fields. A burn up on a remaining time estimate would effectively give you a burn down chart. So swap to using one of those.

You can add "sub tasks" as a field to the issues so you can see them, but they will not appear as lines in a backlog in their own right (because there's little point in having them there - you don't rank sub-tasks outside the issue of which they are a part)

Er, yes, 4 years ago...

A board is not a container (and while we're talking about it, a backlog is actually part of a board, with the card display being a different view of a sub-set). A board selects a load of issues it might work with. Issues do not "move to a board", the board selects what to work with based on the data on the issues. Within…

John and Jack are right, so I won't repeat what they've said, but I wanted to add that the licences are done by people, they are done by service. A service can't be run at two different levels.

There's no promotion I'm afraid, it's "edit, select all, copy" on the source template, then "add new global template, paste and tidy up" in the target.

That's Atlassian access then. You'll need to grant it access if you want to use it.

Again, that is a description of the restriction on that page. Not the space permissions. You need to check the space permissions.

You'd start at https://developer.atlassian.com/server/confluence/

Yes, that "open to anyone" is a description of a lack of restriction, not a thing that overrides the space permissions.

It is, yes, thanks for chipping in, I really should have asked that question when I posted.

I have seen one, years ago, but I think it's been closed with "won't fix"

Um, I think that purple block is actually something you've added to the summary, it's not a Jira icon Try clicking "edit" on the issue and check out what is in the summary field.

There's a "sign up" link in there that gets you an email subscription to a batch of release notes too.

The best way to do this sort of migration is documented in the link you gave! Instead of looking for something else, you would be better off looking at what went wrong when you tried the best migration route, and fixing that.

1. No, absolutely not advisable. Jira can handle it, but your users are going to find it a spectacular pain, given the unreadable wall of text (also making it slow for them) 2. Performance, only on the client side - it'll be slow for people trying to create or edit, and slow for people trying to maintain the list. I would…

Apps like Jira Checklist have their licence details in their section in Admin -> Manage Apps

This sounds like you do not have the space permissions to create or edit pages. Could you check them?

Ok, not the Jira application, but the actual app asking for permission?

That's not something you can "code" for by changing just content. You'd need to be writing apps, possibly even amending the core code in Confluence.

Same place, but the line above is "issue custom field contexts". You might want to check "projects" in the same area.

What development are you being asked to do?

Site admin is not the same as project administration.

It's asking for full admin, not just project. What app is it?

Ok, you need to get rid of that resolution - it's saying "this issue is resolved and not resolved at the same time". There's a lot to do here. First, go to admin -> issues -> Resolutions and look through the list. If there are any resolutions that are not words or phrases meaning "this issue needs no further attention",…

Have a look at https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-custom-field-options/#api-group-issue-custom-field-options

You will find that the issue has a resolution set. If you put anything into the resolution, Jira considers the issue closed and strikes out its key in some displays. This usually happens when someone puts the resolution field on a create or edit screen, but might also be from a workflow that is not clearing it. Check if…

I don't think you mean to install it on scriptrunner, and it's alrady part of Jira. What are you trying to achieve with this installation?

See https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-workflow-transition-properties/#api-group-workflow-transition-properties