Nic Brough -Adaptavist- Expert

I am sorry, but no, it's a bit of a pain when Atlassian get too strict on the "pure" definitions of Scrum and Kanban (my whinges include being able to see Epic names on boards intended for managing Epics - ok, not strictly Kanban, but they're useful, sub-tasks not inheriting sprints, versions, epic fields, and so on from…

There are several types of user-picker field in Jira, and they select from the user-base differently. Assignee, reporter and watchers for example, all work of permissions User-picker custom fields have their own configuration within their contexts. By default, they simply list all active users in the system, they don't…

Welcome to the community! Add And issuetype not in subtaskissuetypes() To the query

I think there's a bug in Cloud label fields at the moment - see (and watch) https://community.atlassian.com/t5/Jira-Software-questions/Custom-field-showing-3-values-instead-of-1/qaq-p/2139851 for a similar report

JQL is for finding issues, it does not have anything to say about what you pull out of the fields on the issues it finds.

Welcome to the Atlassian Community! You will need to add a transition to the workflow, going from "live" to "to do". You should put a post-function on that to "clear the resolution" (set it to "none") so Jira recognises the issue as open again.

Welcome to the Atlassian Community! You don't get licences for this, you have to take your whole system up to premium or enterprise. There's no limit on the devices.

To change the status of an issue, you need to use a transition. So no, you need that All -> Test transition (or <some status> -> Test) However, I would suggest adding a "condition" to it, one that says "only the automation user can do this", which will hide it from your humans.

I'm afraid you pasted (or mis-auto-filled, if you are using a password safe, as you ought to be) your password into your chosen display name when you created the account. You can change and should this yourself at https://id.atlassian.com/manage-profile/profile-and-visibility but I very strongly recommend changing the…

Ah, no, I've just worked out what I missed. It's a Kanban board. They don't work with Epics, they treat them as though they are issues (so the Epic Name is not something that appears on the cards)

Welcome to the Atlassian Community! What do you mean "get" Azure password? What password? Shouldn't you know what it is if you set it?

Ok, so this looks like a bug to me, it definitely needs to go to Atlassian. That labels column should be empty. But could you do one last quick thing for us? Go to the issue view of the issue this is happening for and find the bit that shows us the current value of the field (I'm assuming you have not changed it since…

Jira accounts do not let you use Confluence. Could you please tell us what access these accounts have to Jira? What application access do their "Jira accounts" have? Jira Software or Jira Work Management (core). Or are they just customers with no Jira accounts?

Welcome to the Atlassian Community! The dev-owner display is possible - go to board settings (backlogs are actually one facet of a "board"), and go to "card layout". One section in there is the list of extra fields you can display in the backlog. You should be able to add dev-owner in there. The bad news is that backlog…

Welcome to the Atlassian Community! No, because it's an unmitigated disaster to have more than one person as the current assignee (person ultimately responsible for getting it done). Jira was deliberately designed to avoid that anti-pattern. There is, of course, nothing wrong with "and go ask these people if the assignee…

And what do you get when you try what I asked?

Could you be clear whether these users are customer accounts or you have given them full Jira accounts (whether for JWM or Jira Software)?

No, I was asking you to tell us how many options it offers to you when you start typing the query. Not the results.

So you are going to give them all Jira accounts and let them log in so they can see the issues?

It sounds like you have now created a third account. You need to stop randomly ding these things, take a step back and think about where your data is and what accounts have access to what. * What repositories, projects, and workspaces can account-1 see? * Same for account-2? * And account-3? Which account do you want to…

Welcome to the Atlassian Community! Confluence won't do this to you on Cloud, not until you go way way over the storage limits and your administrators ignore all the warnings from Atlassian about needing to upgrade the plan. You will get it when you run out of disk space on a server/DC install. You'll need to get your…

On Jira Server/Data Center, it's easiest to think of them only having Company-Managed projects. They're pretty much the same on DC and Cloud. In DC/CMP projects, there are three layers of issues to look at: * Epic: has only an Epic Name field * Issue: has only the Epic Link field (Which almost always displays as the name…

Radio buttons work the same way as single-select lists.

Labels fields can hold multiple values, but they should not be duplicated. My guess is that there is something odd in your label names, like alternate characters or nonbreaking spaces. Quick test - go to advanced search and type in GSS Code = "N and see how many options it offers in a drop-down.

That's exactly the message you get when Jira can't find an account with "create issue" based on the email address of the sender of the email. Either the email address does not have an account, or the account does not have "create issue" in the project (actually, the message here is implying that a user has been found, but…

I'm not sure what the customers have to do with this status. The issue status is not something customers have access to.

Welcome to the Atlassian Community! Assuming assst is a miskeying of "asset", then Jira Cloud premium has "Insight" built into it.

That suggests your field is a cascading select - you will need to set the parent half of the field as well as the child option.

That's because the Epic name field only exists on Epics. Try adding Epic link instead.

Not the most helpful of answers, but it's the same way you do it to base issue level issues (sub task parent issue types). As you're on Cloud, there are two quick helpful answers - if it's a company-managed project, ask your administrators to add the fields; if it's a team-managed project, you can do it via project…