Nic Brough -Adaptavist- Expert

I suspect your user is not fake, but simply de-activated. This means it can't log in, and can't be selected from, but if it has been used (reporter, assignee, user picker, etc) will still appear there. Forget the organisation, log in as an admin and go look at the list of users - do they appear in there?

Start with https://www.atlassian.com/software/jira/pricing

I would lean towards a single monolithic automation, sort of. The reason for this is that automations may not run exactly when you think they will, and you may find some of your automation has dependencies on earlier ones (by the way, you "set the workflow" by selecting the issue type, not with an automation) I would also…

Queues are based on filters. You don't really "assign to a queue", you have the request have data that the queue selects for. In this case, you will need something that can look at the incoming email address, and work out how to get a queue to filter on it. When I've done this before, it's been a script to pull the domain…

Welcome to the Atlassian Community! You can do some automation to try to prevent people having more than one issue in a status, but its complexity will be proportional to the complexity of your workflows, and a much better option is to simply allow people to do it, report on "assignee = X and status = Y" regularly, and…

Welcome to the Atlassian Community! See the version list for the compatibilities of the various versions. 

Welcome to the Atlassian Community! There are a few problems with this question: * Sprints do not belong to projects, not projects to sprints * Kanban boards do not use sprints * Projects do not (yet) have a default board * Epics do not go directly into sprints (usually) and may belong to many But take a.look…

Automations put more load on a machine, because they have to be triggered, inspected and then followed, often doing many complex things. Post functions simply run when the transition is confirmed, most don't need to do any of the triggering and inspection work. There is not that much in it, but note that for most Cloud…

Welcome to the Atlassian Community! I think you need to talk to your system administrators. Atlassian Community is here to talk Atlassian, not unlock passwords on systems we know nothing about.

Dell have a moderately complex access system and internal business unit structures. I think @Ted Hung may have landed in the wrong place here, they need to be asking the Dell admins about this, rather than the Community.

It's not "not designed", it can't be done, because it would make the sprints into things that clearly are no longer sprints (and would break the point of using boards to collaborate)

But that is what the assignee field is for. You don't need to duplicate it into watcher (and remember people can remove themselves as watchers, so you're not solving your problem this way) You have a people problem, not a technical one. Why are your users not being taught that "assignee = currentUser()" is what they should…

Why are you doing this? There's no need to make reporter or assignee into watchers, and when you do, you now have the problem that people can unwatch them. Why do you think making them all watchers will be useful? What problem do you have here?

Welcome to the Atlassian Community! The priority display in the backlog is just the icon, to try to save space in there for other data.

If they are appearing on screen, then that's the problem solved.

There can't be - sprints don't work like that! Boards are supposed to show all sprints that might affect them.

It sounds like your fields are not configured to appear on screen for the sub-task, or they are hidden in the field configuration for the sub-task type.

In this case, your team is "the housebuilders", of which you might assign different subtasks individually to people with specialisations. It does not make sense to have a team on a sub-task, the team should be that of the parent.

Jira doesn't really have a way to do this - to see who has project admin rights, you need to be a project admin! Neverthless, everyone else on the project, the people who asked you to use the project and your system admins will be able to tell you who they are. Ask the people around you!

You will need one of the Scripting apps to do this, because you're going to run over an array stored in a field and drag out all the elements, executing code for each one.

I can't - you need to refer to your files via a listing of their network share locations, not a local file location, and I can't know what you've set up!

There is nothing in Atlassian that can do that - the only way to do it would for be you to provide them all the possible email addresses you may have used to create an Atlassian account. If you mean all the Atlassian systems you may have created, then log into my.atlasian.com and look to your products list.

Correct - each application needs a client cert to access the other one.

Welcome to the Atlassian Community! No, this can't be done. Atlassian expect you to use templates to create new pages with blocks of content pre-definied or prompting you for details - instead of "copying and pasting" from old meetings, you could just use the built-in meeting template, or define your own.

You say you are on a standard plan - these do not have archiving functions, To "archive" on standard, you set up a permission scheme that makes the project generally unavailable (browse project limited to administrators for example) and set it on the projects

You can't have an issue with the same id in the database, not unless you are using an unsupported database that you shouldn't be. Again, the best thing you can do is stop looking at the database. It will not work the way you are expecting.

Welcome to the Atlassian Community! If the account already exists, you don't need to create it again. Try the "return to log in" and then log in with the account (there's a "forgot password" link on the login screen if you need it)

A real product manager doesn't really care about the money, they should be all about the experience for the people using your stuff. But, there is, of course, some overlap - you don't want your product managers taking your product in a direction that your users are not going to like. Jira, like most other issue-trackers,…

The backlog will add up story points automatically when you use a Scrum board, because that's where you do the sprint planning. The board does not have a display of the accumulated estimate for a column. The argument is that it's not actually of any use - the team doesn't care what the estimates are during an active sprint…

It means whatever your organisation has says it does. We cannot tell you what that might be. You need to ask your people what it means to them