Nic Brough -Adaptavist- Expert

Welcome to the Atlassian Community! We cannot help without knowing what the errors are and what you mean by "connect Jira to Excel". Could you give us more information please?

Welcome to the Atlassian Community! My understanding is that Atlassian will back up all the Trello systems (and the others) they are going to sanction, and keep them for at least the standard backup time. About 160 days if my memory works. I do not know if they will keep them longer, so that they might be restored once…

The snippet you are showing in your screenshot is the log. You need to be reading the whole thing, not just guessing at one part of it.

Welcome to the Atlassian Community! I assume by "pipeline", you mean a backlog, or a column in a board? I'm confused because Jira doesn't have pipelines, and even if my guess as to what you mean by it is correct, you've always been able to move between columns. "I've tried removing all ranking specifications from the board…

You are very unlikely to get this right by wedging javascript into Jira. Obviously, I'll recommend using Behaviours in Scriptrunner, but that does not work absolutely everywhere. A better option is to simply use a cascading select custom field.

Welcome to the Atlassian Community! Admin means admin. It does not mean "do everything". You will need to grant them "create issue" permission as well.

Look at the rest of the error - it should tell you which line in your script is making the call to the Jira API that is throwing that snippet. People generally won't want to read your entire code to understand it and then looking for errors, when you could just tell us what line starts the error off

Welcome to the Atlassian Community! What errors are you seeing in the logs?

Sub-tasks have no use in a sprint backlog - they can't be ranked outside the story of which they are a fragment, and they have no estimates. They're mostly noise. You can display them though - if you choose one of your backlog fields to be "sub task", they will appear on the card in the backlog

Welcome to the Atlassian Community! First obvious question is "why?" Also, you've tagged this with Cloud, where you have no access to the database, so I'm going to assume you mean "Server" instead. The field values you are seeing as "?" are either coming out because your SQL tool can't display the width of their data,…

Welcome to the Atlassian Community! Yes, change the board filter to "order by due-date" instead of "order by rank". This will prevent you from ranking your issues, which is probably less than ideal for your team. You could create a second board that uses a filter ordered by the due-date, and alternate between the views as…

We've got Behaviours in Cloud, but it does not yet work with Issue Type (Atlassian have not given us the frameworks we need to be able to do it, but we're working with them on it)

Welcome to the Atlassian Community! If you want any constructive help with this, you should probably * Explain the detail of the problem * Explain what is not working for you * Explain what you think a "web login" would solve the issue * Not insult people

Technically, yes, the apps are usually the same code for Server and DC. But you will not be able to get lenses for server apps.

Repeating the question will not help. We've already told you that you need to read the logs for the actual errors.

Could you explain this a bit more please? You do not add validators to post-functions, nor do you do any validation in a post-function (it's too late in the transition). And what are you trying to validate? A text field you ask people to put email addresses in will accept any text you want.

Ok, that is what I suspected - you are using a Linux distribution that does not include git in its repositories. You'll need to get it added. A search for "install git on <my distribution>" is pretty much guaranteed to find you the answer to doing that.

No, that's not right. But I completely understand how you could have got to these misunderstandings - the Resolution field in Jira works differently to the other fields, and we've recently been taking down a number of wildly inaccurate posts made by ChatGPT 'bots that have been posting dreadful answers like the ones I…

Events are things that happen in Jira, they don't have anything to do with users.

Welcome to the Atlassian Community! Hipchat is an old function that Atlassian have not yet refactored out of their code base, just in case people are still using it! The messages you have given us a tiny fraction of the logs, and do not show any errors. Can you start by looking at the logs (you'll find this a LOT easier in…

Welcome to the Atlassian Community! What do you mean by "Nice Day Meeting"?

Um, that link is to a Confluence Cloud table improvement. Assignee has to be an individual. It cannot be a group, so you can't make a component lead a group. I doubt Atlassian are ever going to change that - one of the reasons the assignee field was built that way originally was too many problems in legacy issue-trackers…

I've seen this before, it was all about clashing admins. Default to 40h working week, an inexperienced admin didn't realise it was a global setting, and set it to a 35h week for a project. Another project spotted it, but it flxed itself when the admin realised what he'd done, or anyone else noticed it!

If you can't change stuff when an issue is in a certain status, then this usually means that you have a workflow that is blocking the permission you need by using workflow properties on the status.

Welcome to the Atlassian Community! The question has confused me, the summary reads like you are trying to apply a parent to an Epic (so to a layer in Advanced Roadmaps above it). But the body sounds more like you are trying to add a base-level issue into an Epic?

You are allowed to sequence them. The problem is that you're adopting a clunky, slow, and non-responsive way to do it. Use ranking, use links to establish the blockers / dependencies / order, os subtasks to indicate bits of story that need doing. Sequencing is the wrong approach, in every case. I can't think of an approach…

Scriptrunner and others also require you to add the transitions to the workflow before they can use them to bypass others. But there are ways to protect the new transitions from the humans, so they don't see them.

You can do this without notifications if you get a bit clever with custom events. If you create a new custom event (call it something obvious like "do not use me"), and do not set it to do anything in notification schemes, you can use the CommentService.deleteComment and fire that event - no notifications will be sent.

All of this seems like you have not quite grasped what Agile is for (and Epics within it). You're still thinking in a Waterfall manner where you plan at the top level (Epic), and then try to chop it up into pieces to be allocated out. In Agile, your product manager works with the customers to find out the various things…

Welcome to the Atlassian Community! This is actually the other way around - Jira does not lock status across issues by default. You have an automation, project setting, or script, that you need to turn off!