Nic Brough -Adaptavist- Expert

Nice! I always get the authentication wrong at least once when I'm coding. Attachments are at https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-attachments/#api-group-issue-attachments - you'll find a lot of other stuff in that API doc as well!

Yes, you will need to get the Oauth sorted - the basic authentication is no longer available (it's not as secure as it should be)

How are they "including their email in the request"?

Welcome to the Atlassian Community! No, it has not changed, and almost certainly will not in the future.

Welcome to the Atlassian Community! Your guess is exactly right - time tracking is not a custom field and you get to system fields differently. From memory, try issue.setOriginalEstimate() - bear in mind this thinks in seconds, not hours or minutes.

Welcome to the Atlassian Community! Have a read of https://docs.adaptavist.com/sr4js/latest/get-started/upgrade/upgrade-jira

Yes, that's because the validator happens after the questions are asked of the user, there's no way a screen might know what your validators might be doing. There's nothing you can do about this ordering, the only "fix" is a mandatory description or not running your validators.

Ok, then yes, you're going to lose it if you move to any type of project that does not have forms. It's not the issue description field.

Oh, via Scriptrunner (the console is part of SR, not "the Jira console", so I thought you meant something else. With a list of IDs, absolutely, yes. It's been a while since I worked with it, but I think you can use PortletConfigurationManager to both get the whole gadget object and then delete it. 

You can not do this. And certainly should not be trying! There are fields that exist only for Service projects, so you are always going to lose them. If you're swapping from team-managed to company-managed, fields are not implemented the same way (albeit global CMP fields are now available to TMPs if you re-use them) On…

Most common one I've seen is pretty much what you've done - an issue link between the issues, often called "Deprecates / Deprecated by". For one of them, I helped build some scripts to show data from these links in searches and on the issues themselves.

Welcome to the Atlassian Community! You will need to talk to your administrators - they are the only ones who can add apps to Atlassian cloud systems.

I have https://blog.developer.atlassian.com/creating-a-jira-cloud-issue-in-a-single-rest-call/ in my bookmarks. You'll need to use the Oauth authentication though. Start with a skim of https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/

There is no way to do this other than deleting the entire dashboard. Do not touch the database, you will almost certainly corrupt it.

Three thoughts: * It was possible to change the export file name format ages ago, but I seem to remember it went away at some point. * I always used "logrotate" to kill them off. But yes, cron is easy too: * A set of old files I need to archive, rather than delete, but: * find /mnt/data/atlas/db -name "*.zip" -type f…

Welcome to the Atlassian Community! Nip over to https://www.atlassian.com and have a look through the various products. The difference between Jira and Jira Align is simple - Jira is an issue tracker, Align is something that scales up and is for being Agile at scale (and often has Jira doing the 3 lowest layers -…

Sometimes, it can take a little while for the indices to catch up, especially if it's a large amount of data to empty from the trash. If you give it a bit of time, you should find it disappears eventually (I've not seen it take longer than a couple of hours)

Go into the workflow that has been broken, edit it, and either re-associate the correct status with the step, or rename the "sales" status back to "Done". Before you do this though, take a look at the last editor name on the workflow - you probably need to talk to them, because if you just do either of those two, it's…

Welcome to the Atlassian Community! This depends on what you are using for user provisioning in your Cloud system - Atlassian Accounts (like the one you used to write your question here), Google Accounts, or Atlassian Access (probably hooked up to an active directory or Okta or some other external directory) If it's…

Welcome to the Atlassian Community! There is a strong element of "Jira speak" in this question. * Move in Jira means changing the project an issue is in, or the issue type (or both). You do this from the options menu on the issue view. * Transition means changing the status of the issue, either by hitting a drop-down,…

Welcome to the Atlassian Community! No, there's no way to do this directly. There is actually only one field on the screen - it's a compound field containing several others, and displaying more as it calculates them.

I am sorry, but, no, you do not. Only Atlassian can see the Atlassian Cloud database. I've already explained what I think you mean in the original answer. And I can't answer the question until you can tell us what type of link you are talking about, as they're done and stored differently.

The usual way to "duplicate" information from one page to another is to not copy it, but include it. Have a look at the page that is taking up the data from another page, and edit it. I think you'll find it just says "include : <name of source page>"

Yes, your admins should be checking up on the global list of automation to see what is being used heavily or lightly. Something most places have baked into their monthly housekeeping routine.

One of your admins has edited the workflow. Only Jira admins can edit the workflows in company-managed projects, and the project admins in team-managed projects. Look to the bottom left of the screen to see which type you are in (if nothing there, it's company managed) You will now need to contact them and ask them to put…

Welcome to the Atlassian Community! It makes perfect sense if you have defined tasks to be at the same base level as issues in the hierarchy.

Welcome to the Atlassian Community! You have set up the sub-tasks to require an estimate, but your automation is not setting one. Either make it optional, or add the estimate field to the automation.

Welcome to the Atlassian Community! We'll need to see the actual errors, not the list. They should appear elsewhere in the results, but if you are not seeing them, then you will need to read the application logs (<jira home>/logs/atlassian-jira.log - it should repeat the errors you've got on screen too)

Yes, it will be made unusable. It can usually be reactivated easily by re-subscribing within a few weeks, and Atlassian keep the data for a while longer (122 days minimum, which is harder to re-subscribe too, but can be done)

Welcome to the Atlassian Community! There is not a lot you can do about that - the whole point of Epics is that they cross projects!