Nic Brough -Adaptavist- Expert

Ah, yes, sorry, I was confusing Bamboo with something in another question. But the principles still apply: * Is your config file correctly formatted (with the new licence)? * What does the application log say the problem is?

What does the application log file say the problem is? You don't put licences into config files, so doing that might actually be the problem - a corrupt config file could stop the startup.

See https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-attachments/#api-rest-api-3-attachment-id-expand-raw-get

Can you show us what you get when you cllick on "project settings" and then "request types"?

Um, no, you're contradicting yourself there. You really are telling us that you are trying to email a deleted account. " I sent invitations to her job email (not related to Atlassian). The Atlassian account was created using her email and was deleted later" That is very clear. You are sending email to her account. You have…

I don't think "issue" is a good word to use for Jira issues, but it goes to the top of the list because it is less bad than most others. Story, Ticket, Request, work item, etc - they're all quite narrow definitions. You don't get stories, tickets or requests in manufacturing projects. You don't get work items in support…

> I have sub-tasks in the items, but they are tracked in another board. So the subtasks don't show up in the scrum board No, that's not a bug. Sub-tasks are not separate sprint items, they are a part of a story which is the sprint item. If you exclude sub-tasks from a board, you logically can't complete their parent,…

I am still not sure I understand. You are trying to send email to an account that does not exist any more? Is that right?

The permissions that are being added back in are required for automation and other apps to do their jobs. The warning about the service desk team role is there to tell you that you've mis-configured the project and you need to add the permission back. This happens because JSM is a layer over a core Jira, and the core Jira…

You do not. You should not be looking at a Jira database, it's a complete mess as far as reporting and data relationships are, and it is the worst possible way to look at a Jira system. As for write. No. No. No. No. You will probably get it wrong, and if you do, you will corrupt your system, possibly rendering it unusable,…

No, you can not set the issue sequence in the REST API, and you should not have done it with your code either. Unless you've updated all the other things you need to, you have probably broken your Jira. Jira determines the next free number in the project. If you need to keep a note of the issue id in the old system, import…

No, I wrote that JQL is for finding issues. It gives you a list of issues that match some criteria. It has nothing to say about the data on the issues, tha'ts handled by your reporting function.

This is what it says it is - if you go into the UI and try "create issue", you will find that the affects version field is not asked for. Either remove it from your REST call, or add it to the create screen so it can be filled in. (There is one other way to get this message - it might be that the user account you are using…

Log in as an admin, use the admin cog at the top right, then hit the "admin search", either by clicking it, or just pressing . Start typing "troubleshoot" into the search box.

There is no reason to do this. The "create issue" button does not "bypass mandatory fields" unless you've kludged "mandatory" into the system in the wrong way. If you have used the field configuration or a validator to make your fields mandatory, then this "create issue" route will respect that. If you insist on doing it…

You will need to read the application log - SR logs there when running, even when it doesn't log stuff you can find in the UI. If you can't find a SR error in the application logs, that tells us the script is not being run.

No. A project only has one permission scheme. I'm not quite sure what you are really asking here.

Have you tried it again, making the right selection?

For CMPs https://support.atlassian.com/jira-cloud-administration/docs/work-with-issue-workflows/ For TMPs, https://support.atlassian.com/jira-software-cloud/docs/manage-how-work-flows-in-your-team-managed-project/

Welcome to the Atlassian Community! We can't really help with a problem when you don't give us any information. "It throws an error" is useless to us. Is the error a "nope", "a string of garbage", "a penguin taking a nap on the keyboard and biting me if I try to shift it"?

This is a bit of an odd one to explain, but it's the logging that is not helpful, not an actual bug. The log says "The database is not yet configured" and immediately after, "Startup is complete. Jira is ready to serve.", but that's misleading. The second message really should be "give me a minute, then go to the base url…

This suggests that you're not an admin or agent in the project, so you don't have the rights to amend the request types.

The backups do what you expect from a backup - they back up everything. If you want a partial migration, you'll need a different approach - the JCMA, CCMA, project configurator etc, all enable partial moves rather than having to do everything.

Did you type it, or copy and paste? I've had it fail when pasting it in. Just typing [bob]() followed by a space, line feed, enter or a full-stop works fine for me.

Welcome to the Atlassian Community! Yes, but your plugin will need to incorporate a Python executable environment. Jira doesn't have one (it's not written in Python)

I am not sure I understand what is happening here. The way I'm reading this comes down to "you're trying to send email to an account that has been deleted". If the account has been deleted, then there's nothing going wrong here - you shouldn't be able to send email to a deleted account.

To add to what @Clark Everson and @Craig Nodwell have said, there is currently a bug on Jira Cloud where boards do not show sub-tasks from team-managed projects (not Server or DC, because they don't have team-managed projects)

To expand on "things don't work that way", it's a good thing to understand what a board (and its associated backlog) is - they are not containers for issues, they are a view of a selection. There's no "board position" or "backlog position" field (that is of any use to a human), the position is a function of how you're…

I'd start by describing the actual problem, we can't help with "it doesn't work"

See https://community.atlassian.com/t5/Jira-questions/Is-there-a-way-to-create-JIRA-issue-creation-automatically-using/qaq-p/2068393