Nic Brough -Adaptavist- Expert

No, when you move an issue from one project to another, it takes the next empty number. It does not matter if you are moving an issue back into a project you moved it out of earlier

What do you mean by "alias emails"?

Welcome to the Atlassian Community! You can't do this with JQL alone, it doesn't count things. You can script something to enable it though - what you need is a custom field with "reviewer count" in it, so your script should trigger on issue edit, look at the reviewers field and put the count into the field. Then your JQL…

Run a search for the issues, then use "bulk edit" from the tools menu at the top right of the display to change the ownership.

There is no "deployment quality" function in an off-the-shelf Jira. Your administrators have added it, either as a custom field, or with an app. You will need to ask them what they added it for.

Yes, you do need to be careful with permissions, ideally you should use a copy that preserves them identically. * Stop Jira * Copy the directory and its contents to the new place (this is keeping a backup in case things go wrong) * Set the ownership and permissions to the same as the old one if the copy process changes…

It is not stored directly, the SLA displays are calculated when needed, from the SLA rule and issue data You will either need to recalculate the data or use the API to get it.

Read it from the UI which can give you the actual information you want to be using to do your pre migration housekeeping.

And what user directory?

The really easy answer to this is just "use it". As a user, you will find all sorts of interesting ways you might want to try out and as an admins supporting those people, you are going to get asked a lot. I have been here a while and I am still learning from "can Atlassian stuff do ..." questions daily Play with it, try…

This is something that you probably don't want to be looking at in Jira. It's more a "user directory" function. Jira can use all sorts of directories for users, but it does just look at the basics. There's nothing in Jira for doing expiration, as most people use external directories. Some of them have expiration functions,…

Ok, there's no explanation of why you're doing it this way, or what you're trying to achieve, so I assume you don't want to tell us. (Which is absolutely fine, I generalise when talking about my clients on the assumption they don't want me to share, and they mostly have very good reasons for not wanting to share) You will…

>IF project is marked as done in JIRA. Projects do not have a status, so I'm a bit stuck on exactly how you are marking a project as "done". My guess would be that you have a project for tracking other projects (with each project issue in that project having a status), so the status and status category can be used to…

You will need two separate licences, one for each instance. As Joseph points out, this is going to be expensive for you as you'll need a 500 user licence and a 2000 licence. Have you considered firing up your 10 users with a Cloud instance instead? What is the reason you need two different installations?

Yes, you can do that, your projects with the wrong format will not be able to be connected to Bamboo, but the ones that conform to the standard format will be fine.

No. It is one production licence for each cluster.

The quick filters work as an AND because they're only useful for drilling down if they work together. Your need is easy to meet though - create a quick filter with JQL that says "assignee was Person X or assignee was Person Y"

People usually simply use the UI to do the change of workflow. It's not something you should be changing often for it to be worth automating.

Scripts for server don't work on Cloud, you have to do it very differently. I should have given you this instead: https://library.adaptavist.com/search?platforms=cloud

You say "I get it, you believe it is an anti-pattern for scrum. " No. You have not read what I wrote before about sub-task estimates working fine for scrum.

What user directories are you using here? There is a problem with site access, but how you might fix it depends on what Jira is using for the user list.

That's one of the things the Community is for, in my opinion. The main thing here is to connect with other people (on the premise that we're all using Atlassian stuff), and a close second is "help people with their problems or questions with Atlassian stuff". Marketing is not really what the community is for, but it…

Ok, it's step 5 that is the problem. You can't just flip a workflow over, there's a huge pile of compatibility checks you have to do (and where the workflows are not compatible, you need to give Jira more information). You very much are doing a migration here, but your code does not take account of that. You'll need to…

Welcome to the Atlassian Community! It depends on what you are using for the user directory. The email comes from the user directory, so you'll need to change it in there. What do you use for your directory? (Cloud can work with unclaimed and claimed Atlassian accounts, google accounts and Atlassian Access, which in turn…

Trello is a service that runs on the Cloud, not your local machine. So, no, you have to be online to use Trello.

Scriptrunner can do most things automation can do, but you do have to write code in order to do anything very clever with it. A good starting point is "borrowing" scripts from https://library.adaptavist.com , when the built-in stuff doesn't handle it.

The way most spam filters work is by scoring points on a wide range of things in a posting. New user who hasn't posted or engaged with others before, posting the same thing repeatedly, posting stuff that doesn't mention Atlassian, posting in the wrong category, and so on, all contribute to the score. Links to possibly…

So that's a very long post on just how not to be agile or do scrum while pretending to, so rather than an essay and diving into detail, I'll try to get down to the root of your misunderstandings. >Breaking stories into tasks is often mentioned as part of sprint iteration planning.. Some guides warn about it not becoming…

There are a number of reasons a post might disappear from view in the Community, and almost all of them fall into "it looks like spam", or "it's a non-attributable advert". Whatever your posting was about, I can say that writing it in Finnish was not the problem. The community does not care what language you write in, only…

>The point of my feedback is that claiming estimates on sub-task is "not-quite-scrum" is a misrepresentation. How? Scrum doesn't even mention sub-tasks of any shape, it looks at sprint items alone. Which sub-tasks may be part of, but are not sprint items themselves. >The ask is for Jira to change how it calculates a…