Nic Brough -Adaptavist- Expert

Bear in mind that Behaviours can only control edit in certain places. People will still be able to edit in other places, and it can't stop REST access at all (it's done by the browser, and even when it is working, users can override them)

"Decision date" is not a system field, it's a custom field (added by an app or an administrator). You'll need to use the custom field smart value.

Automations respect the restrictions on issues, so check who the "Automation user" is - the account that runs the automation matters. You'll need to include them in the "restriction" (I'm not sure what you mean by that though - project visibility? Project permissions? Issue security? Workflow conditions?)

Try just putting in the old issue key into the quick search. It will redirect you to the new place it has landed. Unless you don't have permission to see it in the new place!

Team managed are very different, you don't get an issue type scheme, you configure each issue type directly in the issues section. You can add a single sub-task type in the config. What "drop down filter on the board screen" do you mean here?

Yes, Agent licences are not the same as Jira Users or Jira Developers (I think of Users as people licenced for Jira work management, and Developers as those licenced for Jira Software) Cloud does offer a limited number of Agents, and they're expensive compared with the other two, but your customers are free and unlimited -…

Ok, that makes sense, but we can't help you. This is a question for SMobile, not Atlassian - Atlassian can't possibly help a remote application user enter their addressing correctly in an application that isn't theirs! You'll need to ask how to set up your MDM to pre-fill the correct urls!

Use the REST API to read the data you need!

Welcome to the Community! You'll need to get the bugs in the extension fixed frankly, there's nothing Atlassian can do to stop the extensions stomping on their code. Most of these type of extensions have whitelists or exception lists, so adding "don't run on *.atlassian.net" will fix the problem with the extension. But you…

Ok, there's a misunderstanding here: You say "All boards are associated with same workflow". No, they are not. Boards are a view of a selection of issues, not a container. Projects are issue containers. There is no workflow for a board, an issue follows a workflow, and which workflow it follows is configured by the issue's…

If I'm right about this, then it is not an Atlassian problem, but a git one. Can you check if you have an empty .git file in your home directory or in the current directory? If you do, remove them and try again.

I would recommend not doing that. Issue move is for genuine mistakes and housekeeping, it's not something you should be doing as part of a process. Between some types of project, it's not so bad, but moving issues out of a JSM project is not a good idea - you lose the request it is associated with, making the customer…

Ok, there's a couple of things that feel wrong here. "omething equivalent but at a story level." - that is already where you should be using story points, as Stories are what you estimate, plan and execute against. Slightly concerned that you're not doing that already. >when we estimate planned story points we will enter,…

You've said you are on Cloud and using LDAP, which means you must be using Atlassian Access. You'll need to decommission the connection your Cloud Jira has in there and work out how to migrate all your users to Atlassian or Google accounts. I'm not sure that is what you really want to do - it's a big change to your systems.

Yep, feel free to use https://library.adaptavist.com/search?term=handler to find some sample scripts for email handlers - they should get you started. First couple of hits were about parsing data into fields already!

Nope, you don't understand how it's working. But reaching out to your support is the right thing to do.

The status transition codes are not enough on their own. Every one of them needs to be read within the context of the workflow they are in. What exactly are your team trying to report on? Why are they not reading the issue history?

There was, but you won't find it downloadable - it's from the early 2000's! Jira Core has been with us since 2004! I don't think you mean "prototype", I suspect you mean "trial", so you can give it a go - there absolutely is a trial - sign up for one of the Jira systems at https://www.atlassian.com/try Bear in mind, "Core"…

Welcome to the Atlassian Community! I think you might be in the wrong place - you've not explained what any of this has to do with Jira, so we're not sure what you're asking about. Could SMobile be using an Atlassian product for documentation or support? And you've clicked on "help with issue tracking system" instead of…

You will need to remove all permissions from Group A to do anything except transition issues, then move all the other field edits into transitions (so have a transition from Open to Open that goes through a screen that includes all the fields you want to protect) and protect the transitions with conditions that only let…

Could you explain how you have modified Trello to support these functions?

Ok, yes, that makes more sense. The permission to set a security level is separate from the actual security level. If someone does not have permission to set issue security, the "level" field will not even be offered to them. A person must be part of a security level for it to be offered to them in the "level" field.

Could you explain what this has to do with Confluence? I don't understand the "hosted on confluence" part in the question.

I think I would be looking at levels of knowledge in terms of how well people (should) know Jira. A standard level user should be able to find their way around, be comfortable with the basics of issue tracking, understand what fields are for and how the status comes from the workflow. Within that, there's a bit more for…

You would have to decouple the Jira or Confluence from the user directory you are using, and swap to another one.

That sounds like you should know automatically what group it is currently with from the status of the issue.

Um, as I said, you can't do that. Issues in project n*1 can only show and use the components in project n*1, they can't use the components from project n*2.

No, assignee is deliberately built to be the single person currently responsible for the issue. This is by design - in the real world, you absolutely do not want to have multiple assignees, it simply does not work, you will always end up with "I thought another assignee was doing it". I've spent a good chunk of my time…

Welcome to the Community! The short version of this is simply "add a new status to the workflow, and map it into the board (probably in the 'done' column as 'archive' suggests you no longer expect to work on it)" For more detail on exactly how you would do this, we'll need to know if you are working in a company-managed or…

Welcome to the Community! Yes, this is what we would expect. Cloud systems use a shared user directory system, the users are not actually "in" Jira or Confluence, they are in the directory, and Jira and Confluence read the directory. When you are deleting a user, you are deleting them from the directory that both…