Nic Brough -Adaptavist- Expert

There's a long boring story about how scripted fields work, but it ends in "do not use scripted field results to calculate other stuff on issues - you might not get the right answer". Imagine you have a scripted field that is "number of days elapsed between the issue got assigned to someone, and the current due date on…

Start at https://support.atlassian.com/jira-service-management-cloud/docs/what-is-the-change-calendar/ There's no costs or installation - it's built into JSM.

Company-managed projects can do different types of Epic, as long as you are using Advanced Roadmaps to define it as such - the projects and boards still won't see it as an Epic

You should never assign to a group - leave the assignee empty until you've got a real person to take responsibility for it. By all means define a group picker to help you decide which group needs to pick it up (if you use a group picker, you can then get clever with restricting the possible assignees to the members of the…

Mmm, that's not a good practice (and it's forbidden in some industries), the assignee should be the one single person (currently) responsible for getting an issue done. You can't create an account with a group email with SSO enabled (it's actually one of the security benefits of SSO - it blocks you from doing this)

Arguably not a cartoon, because it's a stop-motion animation rather than drawn frames for the series and the first film (the second film was a computer generated cartoon), but Dougal instantly sprang to mind. For those not familiar with "The Magic Roundabout", Dougal is the dog in the middle, I've chosen this image because…

Do you mean updating the service, or going back to Atlassian access to refresh the list of users and groups from your LDAP service?

By "assignee filter", I think you are looking at the default "quick filters" that some boards have. These are there to allow you to filter by possible assignees for the issues on the board. They're not looking at the actual assignees on the issues, Does that match up with what you are seeing? Or is it totally wrong (if…

Is this related to the access problem discussed in the question?

If it were a Cloud install, you have the option of giving people "site admin", but that would let them add themselves to your systems too. On server, you could move to using an external user directory, but again, people with the rights to admin your user directory could add themselves.

The best thing you can do here is to talk to the team's scrum master - they should be educating the team about when they should be adding things to a sprint.

Always minimise them, the aim of Jira is to track issues, and that's best done by asking people to fill in everything they can without forcing them to have to think!

There are only two things that could be doing this. A project admin is removing you, or an administrator has written a script or app that removes you. You need to find the person responsible and ask them to stop doing it.

Admin rights can't be broken down that much. Jira has three types of administrator - system admin, jira admin and project admin. System admins can administrate everything, Jira admins have a smaller set of rights and project admins can only administrate the projects they have permissions for. Note, on Cloud, only Atlassian…

This depends entirely on how the team thinks of sub-tasks. It's a very simple question though. A sub-task is part of its container story, not an independent item. Are your tasks and bugs genuinely a fragment of their containing issue? In your process, do they need to be completed as part of getting their issue done? If…

You can identify the project of an issue by looking at the issue's key or by searching on the project field. Boards can even do swimlanes by project. A label or component would be redundant, just making extra work for people who would have to remember to populate it.

Where did it vanish from? A board? The issue view? The issue navigator?

This is not possible at the moment. You have to create a new Company Managed project, and move all the issues from the old project into it.

What is providing the scripted fields? Scriptrunner or JMWE or something else?

Yes, you did, but how you've ended up with way too many options for your people is not important. The point is that your field is probably useless to your people.

To add to @Mikael Sandberg 's advice, you should be aware that humans struggle with most lists longer than about 42 items. Cloud Jira actively limits the number offered. Your 5400 list is unlikely to be of any practical use - you will find that if humans are using the field rather than automation, it's mostly full of…

The custom field IDs can vary - Jira allocates the numbers for all sorts of things as it needs them. So you can get very different ones depending on what the history of your system is. Imagine my first Jira system - it was installed before we had Greenhopper, let alone Agile or Jira Software. When the people who inherited…

It's a name for your humans to get a handle on it. Some of us ask for consistent naming conventions, like including the project or project groups it is intended for, or something else that briefly explains it. I personally usually go for a human short description and include the Jira issue key for the admin request that…

Sorry for the delay in responding, coincidentally having "fun" with Google and Atlassian accounts with a client! Thanks for confirming the questions, it hugely narrows down what might have happened. I am 99% sure that you have (had) two accounts here. The old "Trello" one and the new "Atlassian account". The problem is…

Ok, that tells us it's Scriptrunner, which gives you two places you need to read for errors. First, as we already talked about, your version of SR may not be compatible. Check what version you are on, and upgrade if necessary. Second, it could be the scriip that is failing. You'll need to edit the script and see if it is…

Ask the Visual Studio coders...

What is the behaviour when they click create sub-task? Error message? "can't create sub task" tells us nothing about the problem, it could be a large penguin sitting on the keyboard for all you've told us!

Welcome to the Atlassian Community! There's no way to do this - Jira only records "label added/removed" in the issue history, and there's no JQL that can search for that, nor is it a field you can report on. You'll need to do some coding to extract the date.

That query is nonsense. Epics do not have an epic link field, they can't be included in other epics. I think they might have meant issuetype not in (Epic) and "Epic link" is not empty Although you don't need that either - just " "Epic link" is not empty" will return a list of all issues that are in any Epic.

I'd look for checklists for Jira and then do the automation work with Scriptrunner.