Nic Brough -Adaptavist- Expert

Welcome to the Atlassian Community! Are your issues and all their sub-tasks in the very last column of the sprint board? The status and status category are utterly irrelevant here, you need the subtasks to be in the last column on the board.

Hi Luke, Atlassian suggest no more than 500 issues on a board, and most consultants see them become pretty much useless to the end-users at 250+ (information overload, not performance). It's not as simple as this, but the performance of a board is a function of several things, the main one being filters, of which there are…

Welcome to the Atlassian Community! First, Jira Core was effectively renamed to Jira Work Management quite a while ago. If you want to carry on with the same structure, then you will need to buy: DC1: 2000 JWM users DC2: 500 JWM users + 500 Software users With DC2, I would drop the JWM users, let everyone have Software, as…

No, because the number alone is not a unique identifier of an issue, so it's pretty much useless. You have an unusual use for it, one that I do not think you have thought through fully. Your reference could easily end up as non-unique, as you could generate the same one from two different projects with unrelated issues.…

No. It is not fair to use dumps, it breaks the whole point of the certification. If you use them, you may find your certification revoked for breaking the rules.

Welcome to the Atlassian Community! The only thing you can do really is forward any email (one from each domain) to https://www.atlassian.com/trust/report-abuse - no need to add any data or explanation, just forward it. It gets turned into a task for the abuse team to check the site and shut it down if it's abusive.

Welcome to the Atlassian Community! There's a bit of a misunderstanding here. Issues do not move between boards. Boards are a view of a selection of issues, not issue containers. I can see you've partially understood this, because you've got two boards selecting things in certain status, but the other thing to understand…

Welcome to the Atlassian Community! There's a couple of important things here: * You are not supposed to be measuring individual performance in sprints. Sprints are for teams, not individuals. (In some places, it's actually illegal to do individual reporting like that). * More importantly though, one team's story points…

Welcome to the Atlassian Community! No, there's no way to do this, even with Scriptrunner (you could use that to add a button people can click to pop a screen, but that's not going to happen on edits). If you need to control people's access, popups are the wrong way to do it. Jira already has a fine-grained permission…

Either adjust the board filter so that it only includes the assignees you want to see, or add quick-filters for the assignee - these toggle displays of selected issues on and off, so you could define one that says "assignee = person" or "assignee = currentUser()", or even "assignee not in (A, B, C)"

It's the same answer - Beahviours can't run anything before the screen renders - it's working from the data in the screen.

In Scrum, you list a set of items that need doing, and commit to doing them within a sprint. In Jira, the items are issues. It measures your progress on the binary "is it done or not?" Sub-tasks are part of issues, not sprint items in their own right. They are fragments of sprint items, they do not contribute towards…

That error message implies you are doing something with a field, not running an advanced search. Have you copied and pasted just the watcher = currentUser() AND resolution = Unresolved ORDER BY priority DESC, updated DESC into the advanced search

Welcome to the Atlassian Community! One of your administrators has set up either a "create or comment" email handler, or that one of your helpdesk (Jira Service Management) people have added an email channel to a helpdesk project. You will need to reconfigure, or just disable this, to stop the mail getting turned into…

Most of them will need your users who are using them to tell them which Jira you want to interact with. For existing interactions, they'll assume the first one you connected until told otherwise.

Welcome to the Atlassian Community! Just use Jira. It's an issue tracker, and "tickets" are a type of issue it can track. If you're talking about support requests, you probably want to use Jira Service Management as the front-end - it simplifies the interface for customers and makes them free (you only have to licence the…

You may be misreading the laws here. People do have a right to be forgotten, but various states have different rules on auditing, and the "right to forget" is very much over-ruled by "the need to know who did what". In many states (including Germany, which is the example I use all the time because it is very strict), it…

It's mostly not misunderstanding sprints here, it's misunderstanding estimates. But that does break Agile processes when you don't get estimates. Scrum and Kanban are older than Agile, but are good processes to adopt when you do want to deliver something useful now, rather than what you (rightly) thought might be useful a…

There's still no bug here. It now sounds like you have put the issue into a sprint. That means it can not belong to another sprint, whatever the board the different sprints belong to. It's not a filter thing, it does not make sense to have an issue in two sprints at the same time, because that implies different team…

Welcome to the Atlassian Community! Jira does not collect usage data about filters, so the very short answer is "no". Alos, the usage is not simple - a dashboard can make use of many filters, humans may use many filters, filters are used in boards and reports (sometimes without being defined, as the code does it, not…

Welcome to the Atlassian Community! No, they're not cool with it, and they do want to hear about any abusive systems so that they can shut them down. I see that in another of your questions, @Andy Heinzer has already told you to forward abusive emails to https://www.atlassian.com/trust/report-abuse They have a bit of a…

Welcome to the Atlassian Community! If it is coming from an abusive system, then Atlassian will shut it down so that it stops. The team is busy though, and it can take a while for abusive systems to be taken down.

Hi @Raad Haider Removing yourself from an Atlassian system is not possible, as @suren said, you need to talk to the admins. However, Atlassian have a problem with their openness - it's easy for spam/scam people and 'bots to create Atlassian accounts, which can then go on to create systems that they can use to send spam or…

Max Harry appears to be an AI 'bot - all their other answers were written by AI and were wrong or misleading, so they've been removed

When DC was released, it simply matched the existing server tiers to keep the pricing schemes looking as simple as possible. As it matured and people took up DC licences, we could see that almost no-one was buying tiers below 250, and 250 was by far the least popular tier as well. So Atlassian dropped everything under 500,…

If you make the field mandatory AND set a default for it, then "none" will disappear. You have to do both of those - setting a default means the user will see the default option selected when they create the issue, and making it mandatory forces the user to select something. Setting the field as mandatory will leave "none"…

Hi Tom, The global workflows only apply to company-managed projects (via workflow schemes). Team-managed projects have their workflows inside the configuration of the issue type - you will need to go into the project config, then each issue type and edit the workflows associated with them from within the project. This is…

Hi Danielle, Atlassian do not delete accounts owned by other organisations. One of your admins (or possibly the account owner) has asked for this account to be deleted, and it has been shut down. After a while (I'm afraid I can not remember how long the cooling-off time is, but i want to say 90 days), if no-one tries to…

Welcome to the Atlassian Community! What do you mean by "I create a label"? In Jira, you do not create labels and then add them to issues, you just add a text label to an existing issue (or one while you are creating it). When you search for a label, all you need to do is "labels = <label>" or "labels in <set of labels"

Welcome to the Atlassian Community! This suggests that you have not applied the new licence key to the app in your system. Fire up your marketplace account and go find the key in one tab, then open up your Jira in another one and go to Admin -> manage apps -> Xporter, where you will be able to copy the key from your…