Nic Brough -Adaptavist- Expert

If re-indexing works here, then you need to take a long hard look at what you have set up that is corrupting your index.

Welcome to the Atlassian Community! "can't start plugins" tells us very little about what the problem is. We can't really help you without having more detail on what is going wrong. Until we know what the problem is, any "solution" you see is going to be a total guess.

Welcome to the Atlassian Community! Could you explain what this has to do with Atlassian software? This looks like a build or execution error in your code or supporting software. The closest Atlassian gets to that is by acting as a source control management system (Bitbucket) or CI/CD system (Bamboo), neither of which have…

Welcome to the Atlassian Community! What app are you asking about? What does "not able to use it" look like?

Welcome to the Atlassian Community! * Group membership are maintained by the administrators (mainly the business admins, not your Jira admins), roles by the project administrators. * Roles are administrated at a project level. * Roles give your Jira users much more power; they enable teams to be self-governed. * Roles work…

The page tree is quite handy, but I still prefer a landing page with loads of navigation on it! Brant and Andy have got you there :-)

What do you have in the left-hand column? Is there no "pages" entry near the bottom? (This would not solve "blank main page" by the way, but the pages entry is a page tree. I tend to use the main page for other ways of organising links for people to explore - label, contributor and recently updated for example)

Welcome to the Atlassian Community! No, there's no way to do this. Admins can administrate everything. But there are some "delegate admin" functions in the pipeline. It's good that you have a handful of admins, the best way to work here is to keep them in touch with each other, working as a team on admin, and so that they…

I suspect it's because the clauses are evaluated independently, it's not looking at the to/from together. (In range is translated to two independent clauses, a before and after)

Yes, it will let you proceed, but you can lose data and functionality. There is app migration data - have a look at the docs for JCMA - vendors had to work with Atlassian to get it to cover their data.

You won't find this in the API in any single place, you are going to have to retrieve a lot of data and calculate what you are looking for. The reasons for this are * That's not how burndown works - you are likely to find the team doing stuff like burnin down nothing for the first few days and then suddenly burns down 6…

I would start by renaming your "Category" field. Jira already has two Category fields built into it if you've got one of the non-core applications, and that is going to give you massive problems with search already, adding a third one is not going to help. Even if you insist on going back to Category, you may find it a…

You'll find that the issues that move to the next spring are not "done", or have sub-tasks that are not "done". That means "in the last column on the board" (and it applies to all sub-tasks - you need to have them on the board)

No, you don't need to, JPD does not have Company managed projects yet. You need to manage the permissions in TMPs by working in the role settings.

Welcome to the Atlassian Community! This way lies madness! The Jira database is not intended to be reported off, it's a data store, and it's evolved into something that is an utter nightmare to report from. I very strongly recommend that you stop even looking (and change the database password for your read-only reporting…

Welcome to the Atlassian Community! First question has to be "what are you actually importing?" What data is in the CSVs? And what are you expecting the second export/import to do?

Welcome to the Atlassian Community! For an issue to move into the next sprint when the current sprint, it must not be in the last column on the board. Is that how you are defining "finished"? Also note that all of it's sub-tasks, if it have any, also have to be on the board and also in the last column, for an issue to be…

For a simple login, no, that's what the login function in Jira does already and so there's no point in replacing that. You don't have to do "full" SSO if you go the way @Florian Bonniec - Okta for example lets me log in there, then visit Jira without having to log in (but we, for some unknown reason, have not enabled SSO -…

Welcome to the Atlassian Community! I strongly recommend that you stop looking in the database. Its complex, has evolved as a data store, and is totally unsuitable for any form of reporting, because it's rare that people trying to report on it understand it (and there's a very steep learning curve). Go to the project…

That doesn't tell us where you are running this code, or give us the line of script triggering the error.

No, Automation does not have a "move" function. This is because changing the project and/or issue type is a structural thing - all the config hangs off them, and most moves changing the config. They're not really moves, they're migrations, and they tend to need humans involved. The exception is when two issue types are…

Welcome to the Atlassian Community! My best guess is that you are looking at a team-managed project, which are not configured via schemes, their configuration is local to them. I'm not sure Jira Product Discovery has company-managed projects yet.

I'm afraid your only options are to code to work with the other app, or stop using it.

What do you mean by "inserted record"? Do you mean another Jira issue? Or a block of data you want to add to an existing issue?

Welcome to the Atlassian Community! Nothing, there is no "priority". You either grant permission to someone, or you do not. In your example, you've given user 1 permission twice. Which has no effect. If you were to remove the permission from "developer" group, then user3 would stop being an admin, but user1 would continue,…

Yep, you've got complete freedom to create as many different issue types and workflows as you need, it's just that you can not use more than one workflow for any issue type (in the project - you can do "Project 1: Bug : workflow A", "Project 2: Bug : workflow B")

Welcome to the Atlassian Community! I'm afraid it does work, there's nothing to update. You are putting your code in the wrong place (see the conversation about listeners), or not using the issue object correctly in your code.

Welcome to the Atlassian Community! All you need to do is convert the milliseconds result on the last "return" lline into seconds (dive by 1,000) or minutes (divide by 60,000)

You can use automation to copy the QA assigee into the assignee field when the issue moves into QA

Welcome to the Atlassian Community! The easy answer to the last part of your question is as simple as "edit the workflow, click add transition" The longer answer is for points 2 and 3, but it's the same answer - create the transitions you need for all the actions, and then, as you say, add "conditions" to them. The one I…