Nic Brough -Adaptavist- Expert

It doesn't matter that we're talking about best or standard practice. The point is that multiple assignees for an issue simply does not work, ever, and hence the software does not support it. But it does support teams fine. * One of the things sub-tasks are for is breaking up stories so that fragments can be assigned to…

"Show details" doesn't show edits of cards. There's no real history in Trello, it's not an issue tracker.

Welcome to the Atlassian Community! Most personal IP addresses change regularly, as ISPs are short of ipv4 addresses to use. Mine changes roughly once a month. But they will stay within a range of addresses the ISP "owns" Atlassian are blocking ranges of IP addresses, but they do it across the board - if it's an Atlassian…

A diagnostic question - where are these issues "showing as <status>"? I assume by "complete list of issues", you mean you have run a search for the issues and they are showing "In progress" in the status column in the issue navigator. Is that right? If it is, then can you pick one of the issues that you think should be…

There is no way to do this. You can't apply rules to people whom you can't distinguish between. Before you identify someone by having them log in, you can't know what group they are in. >What I would like to achieve is to have one single access token which would be shared with all the users That is pretty much the…

Start with a read through https://confluence.atlassian.com/adminjiraserver/switching-databases-938846867.html

There is no way to do this on Cloud, other than asking Atlassian to clobber the database for you (and I don't think they do that outside large migration scenarios for which they, or a partner, would be working with you)

Yes, there's often a difference between Jira-project and real-life-project - it's actually quite rare that a jira-project is a direct 1:1 match with a real-life-project. Stating that, and then giving us the JQL you are working with is a fantastic answer to my request for a bit of clarification. Thank you! When you say your…

Welcome to the Atlassian Community! Jira does not have a native "project status", it works with issues. Could you explain where you are seeing this project status?

Except I missed something. It should be labels != not-active OR labels is empty "labels != not-active" will not return issues with no labels because there's nothing to run the "not equal to" logic against. So... * ( Project in (FP, FNA) OR Project in (X, Y, X) and labels in (fna, fp) ) AND ( label != not-active OR labels…

Your developer licence expires with the Commercial licence it is a part of, but I don't know if they are perpetual like the main licence is. They didn't use to be - one of my old useful tricks was to be able to put an expired developer licence on a system to make it unusable (barring the admin)

First, stop reading the database - it's the wrong way to do any reporting on Atlassian data. So, you say you have a set of issues that are resolved, but show up in a search for "resolution is empty", suggesting that they are not resolved. What makes you think they are resolved? In the UI, not the database?

The error you are getting is quite unfriendly, it's not written in plain English. In English, it means "the confluence.cfg.xml file is corrupt - it is not structured as well-formed XML". That means the code cannot read it. Whatever edits you made to the provided copy not true XML. The error usually, but not always, means…

Always use parenthesis to explain to the humans what the query actually is (unless all of the clause joins are the same - all AND or all OR - we don't need help with those). It's good practice to do it with the computers as well, as humans are really bad at understanding how a computer will read an non-parenthesised query…

The formatting strings are free text, so open to errors. My guess would be someone put in "m" instead of "M", so you are getting "minute" instead of "Month" (in what should be the day field)

No, it's not possible. I don't think it has any use either. Project sequence keys are unique to the project. Why would ABC-1212 have anything in common with XYZ-1212?

Welcome to the Atlassian Community! Smart values only apply in Automations, you can't use them in JQL outside Automation. You can guess the next bit - quick filters use JQL, so...

This is quite an easy question - all the field types that standard Jira applications provide are on Cloud too. If the field type is part of Jira Core, Jira Software or Jira Service Management, you'll be able to migrate it fine. Fields provided by apps - you'll need to check with the vendor. Scriptrunner's Scripted Fields,…

It defeats the whole purpose of an issue tracker, if you can't see who is doing what.

Welcome to the Atlassian Community! Your very first bit of JQL works perfectly for me (albeit with slight differences in data). Until I start adding sub-tasks. Issues of a sub-task type only belong to an Epic by virtue of being part of an issue that belongs to an Epic. They do not have their own Epic link. I suspect your…

Administration rights means admin rights, not can see/do anything. There's no point creating a dedicated admin account for this, you would still need to go through all your permissions and project roles to make sure the new account has "browse project" 

Welcome to the Atlassian Community! I think you may have clicked on "help with documentation or support system for the robot" rather than "help with robot". We can only really talk about Atlassian things. Добро пожаловать в сообщество Atlassian! Я думаю, вы, возможно, нажали «Помощь с документацией или системой поддержки…

Always my first point of call, but if you want to do it in the background, call the REST API in your code.

Welcome to the Atlassian Community! There's no way to know this. Issues can appear on many boards, and the users could be creating issues from any of them, plus all the non-board methods of creating issues. The "create issue here" function is just a convenience, it's not really "creating on a board" You would have to read…

Welcome to the Atlassian Community! You do not change workflows by editing issues. To use your new workflows, look at the "workflow scheme" for the project. This determines the workflow association for each issue type. Note that you have to do this via global admin, the options for workflows within a project don't let you…

What does my.atlassian.com tell us?

I'd look next at the workflow and users combined - as I said, you can apply status level permissions which could be causing this.

I see. You are having problems with done and not-done issues on your board. You can not "delete" a backlog, there's only one of them, paired with your board. Open issues appear in the backlog. I think you may be stuck with marking issues done, so when you close a sprint, they go to the next sprint, or back into the backlog…

If I understand this correctly, you are trying to have a "field" which can have many lines, but each line is entered separately, like adding rows to a table. Jira does not have fields that do that. You say you need up to 20 lines, so the closest you can get is adding 20 fields, and leaving the ones you don't need empty.

They do not. Jira expects edits to be quick and immediate, and doesn't have anything that says "someone else is taking ages to edit this"