Nic Brough -Adaptavist- Expert

Welcome to the Atlassian Community! The usual reason this happens is that one of your board admins changed the sprint estimate field in the board settings. Changing it back to story points will fix the problem.

Welcome to the Atlassian Community! You will need to talk to your Confluence admins about getting your space permissions set up correctly. Or the space admins for the Space you don't have create/edit for.

I am sorry, but this question does not make sense. Clone what? Whole projects? Random issues? Why would you think you want to clone many issues, is there something wrong in your process?

If you click on "next page" you should see the next 50.

You've got a bit of a problem here, one which can be summarised as "your process is not Scrum". Jira Software's scrum boards are built to support scrum, so they are not going to work for your process. The main reason for this is that scrum does not have anything to say about non-sprint items, and sub-tasks in Jira are not…

This usually means that the account running your application does not have the necessary permissions to run the software. That's something set up in the operating system, it's not a software fault. Is your user allowed to run git on your system? Try running the command on the command line, outside Sourcetree - do you get…

Hmm. The problem here is that what you've posted looks like a very incomplete log. I'd expect another 50 lines, some of which would tell us more! Are you sure it just stops part way through the logging?

Yes, you can - it will take incoming emails and turn them into requests or issues, depending on whether you direct the email to a service desk project (requests) or a software, work management, or product discovery project (issues). It is utterly useless for newsletters. The next question is what are you trying to set up?…

In the settings for the Power BI app. Your admins will need to do it, you can't configure the app without admin rights.

There's no time limits on how long an issue can be open. The hierarchy in Jira is simply Issue -> Sub-task (what you call "task" is just a label for a type of sub-task, you can have many types of Issue and sub-task), but Jira Software adds Epics above issue, and then Advanced Roadmaps allows you to build layers above Epic 

To close an issue, you need to be able to "transition" it from one status to another. This is done in the workflow (the workflow is a set of status with transitions between them). Transitions are protected by "conditions" - rules that say who can or can not use a transition, or what data needs to be present to allow it…

As I said already.

This is going to come across as quite opinionated, but you are absolutely right to look at WIP limits. If you do Kanban, there are no estimates. Every card is a piece of work that needs doing, and it is the same "size" as every other card the team gets. Issue type, an estimate of time, complexity, business value - nope,…

Mmm, because it's a broken idea. Velocity is velocity, it can change a lot. The (mean) average velocity of a team is not really that useful - velocity is there to inform your sprint planning based on what you've done recently, after you've improved whatever was not quite working in the last couple of them. A mean doesn't…

Scripts don't run or compile in the script editor, they run when they are triggered by the actions you have configured them for. What happens if you create Epics in projects with no scripted actions or fields set up?

It isn't in Confluence, you are extracting data from Jira, and that's where the Epic link field is. You need to include it in whatever your table is asking of Jira.

Welcome to the Atlassian Community! Do not adjust the sprint start time, it's misrepresenting what you are doing. Leave it in place, and accept that your people adjusting in-sprint estimates are recording scope creep in the sprint.

Welcome to the Atlassian Community! Jira does not do "assign to group" for any field where there should be a single named person. Reporter, assignee, watchers - all should be individuals, because "assign to many people" is always a miserable failure in real life. There is nothing wrong with having a separate "and this…

How are you exposing the file's directory to the network? You're going to need to write something that can do a "dir" on that shared directory, get the list of file names, and drop it either into the options for a custom field, or into a database so you can use a database-picker field to draw it in.

Welcome to the Atlassian Community! I am a bit stuck on what you are describing. What are the issues showing as their current status? Do they have transitions to the old status?

This is usually down to iffy content in the "text" that can't be stored by the database. Are there any special characters in it at all? I'm looking mainly for emojis or embedded images, but I'd want to just check if there are anything that might be a control character (so if it's not a-zA-Z0-9 or basic punctuation)

Welcome to the Atlassian Community! This is exactly what it says it is - your administrators have configured it to only read certain projects within Jira. You will need to talk to the admins of your Jira and Power BI systems.

Whatever code condition you need. Probably something like "issue type = X"

Welcome to the Atlassian Community! There's no way to do this, each import can only import one sheet.

Welcome to the Atlassian Community! This is not an error message that means a specific error has happened, it's a marker that goes into logs and databases for Atlassian to group together similar incidents happening across many instances of their Cloud services. Best you can do is simply report it to Atlassian at…

Welcome to the Atlassian Community! Are there more errors further down the logs? I've seen those errors when using non-English languages, but it was a while ago. The other time I've seen it was when a system had an app installed that modified how projects work and SR was not aware of how it worked (which I understand has…

That means what it says - your Jira is running ok, but it needs to upgrade the data to match the new version, so it's now ploughing through all the data changes. You should be able to use Jira fine after it has finished. You should be able to see progress in the application log file.

Update issue field will do it, but as you have Scriptrunner, I would recommend using "set issue security level" - it's a bit more flexible and easier to use.

The Clear-site-data should only be used on logging out (or timing out, but that doesn't get done by the server and browser). The cache that it causes it to clear includes the current logged in session and entered data, so having that header on most responses would destroy the ability to actually use the system. There is…

Welcome to the Atlassian Community! Probably, but you'll get a better answer if you explain what JTMF is.