Nic Brough -Adaptavist- Expert

If you have set up Jira to that Epics can go into sprints, then yes, you can simply read the Sprint "field" from the issue.

That looks like the display of "sub tasks in this issue and how many are resolved", but without seeing the rest of the screen for the context, I really can't be sure it is that. If it is though, then it's not a field, it's an automatic display which will appear when you add a sub-task to an issue.

Same applies to Confluence.

Could you do a simple test for us? Create two issues, a Task and a sub-task, in the project you're having a problem with. In both of them, put something into the fields that you've got the problem with. When you view these issues over the API, do you see the content of the fields you entered?

Welcome to the Atlassian Community! Please, STOP SHOUTING, it is hard to read, and a lot of people find it to be rude. You can update your cards from your workspace's billing settings. If you can't find that in the settings, then try going to https://trello.com/<your workspace name>/billing

What does "not able to do the import process" look like? Your screenshot is of a workflow edit screen, nothing to do with import. What is stopping you importing as per the doc @Utkarsh Agarwal pointed to?

A good starter for your own email handler is at https://library.adaptavist.com/entity/create-a-new-issue-using-a-mail-handler-script-and-set-the-epic-link-to-an-existing-issue-found-in-the-mail-body This just looks at the epic link field, but the same applies for any custom field

Welcome to the Atlassian Community! How are you implementing "lists" in your content?

I'm sorry, I was not clear in that question. Why are you trying to change the reporter?

Ah! That makes sense. I thought it might be a script or automation being executed in your name, that was the next thing I was going to say if the history had your name on it!

Welcome to the Atlassian Community! Stop looking at the database. It is horribly complex and rarely works the way that you are guessing that it will. If you want to look at users email addresses, look at the LDAP server, or Jira's UI or REST interface. The database is not going to work the way you think.

Could you explain what a "t card" is?

Jira does not let you set the reporter (or assignee, or other user fields) to an inactive user because the user is not valid any more. SR can't override the core code. Why are you trying to do this?

Jira does not have a lot of reporting on this sort of thing, mainly because it should not happen often, and when it does, your team should be looking at why it has happened every time, and in great detail.

Welcome to the Atlassian Community! What do you mean by "MBs"? We could take a guess, but we can't be sure we'd be answering the right question for you.

Welcome to the Atlassian Community! You will need to take this up with Atlassian's accounts team for Trello, they will be able to kill off the account and system you subscribed to, and refund you for what you have not yet used there. Get in touch with them at https://support.atlassian.com/trello/ and follow the links for…

Yes. The boards are a different visualisation of the issues, with status being the columns. So dragging between columns must be a status change, and status change is done only by transitions in the workflow! The "back end" does not care how you trigger a transition!

See the second paragraph in the original answer.

Start at https://confluence.atlassian.com/jirakb/how-to-update-the-ssl-certificate-used-by-jira-1129680381.html

Welcome to the Atlassian Community! This sounds like you have a validator on the create transition that is demanding you fill the Epic Link field, or you have set it mandatory in the field configuration. You'll need to undo whichever one of those it is.

Welcome to the Atlassian Community! What are the restrictions on the page? Look for a red padlock symbol, and hover over it (remember that admin rights mean admin, not "can do everything and ignore security")

One quick thing to look at before we dive in - what does the issue history say happened?

Welcome to the Atlassian Community! Bitbucket username/password authentication was deprecated over 6 months ago. See https://community.atlassian.com/t5/Bitbucket-articles/Announcement-Bitbucket-Cloud-account-password-usage-for-Git-over/ba-p/1948231

Welcome to the Atlassian Community! How exactly did you "roll back"?

No. JQL returns a list of issues that matches the question of "what issues match these criteria". It has nothing to say about what you report on or how.

You should not close incomplete tasks. It's a very plain boolean - an issue is complete or not. Note that "complete" includes "we did some stuff, but then decided we're not going to do any more work on it, so we've cancelled it. The cleanest way to do that in an issue tracker like Jira is move the issue through the…

Welcome to the Atlassian Community! This error message always means "Jira is not able to reach itself" over the network. On Cloud it is possible to do this if the network you connect to the internet is doing certain packet-filtering on. You need to talk to your network admins and get them to do some packet tracing. On…

So from your list: * Reporter: will be automatically captured * Priority: will be taken as Low/Medium/High, as long as you have those in the project's priority scheme * Title: Isssues don't have titles, they have a summary, which will be taken from the subject line of the email Less about your list: * The description of an…

Hopefully, they followed the advice in the linked article, and that fixed it.

Ok, so when you create a sub-task in the UI, are you asked for these fields? Is it possible to create a test one, make sure the fields are filled in, and then look at it again "over the API"?