Nic Brough -Adaptavist- Expert

Oops, sorry, I forgot to mention one little thing. Because Epics are issues in their own right (and all the objects above them are too), they can have their own sub-tasks. This looks a bit weird - an Epic can have two types of child issue, Issues and Sub-tasks. I try to never have sub-tasks on anything other than…

Welcome to the Atlassian Community! If you convert a sub-task to a story, then it is no longer a part of its parent story. That's why the parent-child relationship has disappeared. Atlassian has recently been changing the way the hierarchy is represented, moving from three different layers (Initiative -> Epic, Epic ->…

Welcome to the Atlassian Community! Which application is this in? If it is Jira, then what type of field is the "affected services" field?

Welcome to the Atlassian Community! You can't do this directly, Jira field's mandatory settings are done inside the application, not by dint of the URL you visit. There are two systems involved here. * In Jira, you can set fields mandatory, which means that they have to be filled in during create, and filled when you…

Welcome to the Atlassian Community! Epics are issues in their own right, and issues live in projects, and take their keys from the project key. If you want to have an Epic key of MG-#, then you need to create the Epic in the project which has a key of MG.

Welcome to the Atlassian Community! The space-settings button is always presented to a visitor, you can not turn it off. This is because it is the only way to reach certain functions within the space that are not pages - reports for example. If your user does not have the permissions, then they will not be offered the…

It is a known problem with some browsers. Is yours a very old version (from over 3 years ago when this question was posted?). Do you get the same problem in a different browser, or if you disable all your extensions in the current one?

Not quite. The aim is to get smaller users moved to Cloud (even though it now supports quite large systems)

No, it's not doing that. It is letting the admins edit their local workflows. Jira supports that in team-managed projects.

Please see the answers already given, there's a logical reason it works this way, explained in those answers.

Ah, good, that's one of the two correct ways to do it (the other is to find an old expired trial licence and apply it to your server - servers with an invalid trial licence work fine, except that you can't create, edit, or transition, issues, and some admin functions go read-only as well) Your errors could be pointing to…

An issue collector can do that. For doing it in a script, lower level means that your code would need to reference calls in Jira's API that get to the data via the field, rather than the issue, and some of that is not documented. You could also do it in the database, but there's a problem with that - you need to stop Jira,…

I would like to add that you can do this for transitions, just not view, create or edit. You can present different screens for people to update fields during different transitions.

Hi Amit, * Jira Server and Jira Cloud are different pieces of software, they diverged years ago, taking two different routes along how to visualise issues. You can't expect them to look the same. * Your second screenshot is of the configuration of a Team Managed Project. These do not support message fields. (Also,…

Ignore the drop-down, you need to say watcher = "the name of a person you know is watching at least one issue" For example, on the ACL Sandbox:

Welcome to the Atlassian Community! This is something you should probably do on a dashboard, not by sending a report via email - the email could be out of date within seconds of being sent. A dashboard with three gadgets (probably all using the same filter for "Project = X") would tell your people the current answers as…

Welcome to the Atlassian Community! You should modify the board filter so that it includes the issues you want to see on the board. Your question suggests that you might be doing something like "Project = A or (key in (B-123, B-345, B-37))". It would be better to have a filter that says "Project = A or (some field =…

Welcome to the Atlassian Community! You need to embed the command to open in a new window in the URL you have put in. For example <a href="https://www.atlassian.com" target="_blank">Atlassian</a> However, it is up to your browser if this opens a new window or a new tab.

Welcome to the Atlassian Community! Does your board filter include all the sub-tasks (irrespective of status) when you run it as a search?

Welcome to the Atlassian Community! You can not do this for some issues. Only issues that have never been in an active sprint can be moved. The sprint field contains all the sprints an issue has been in, not just the current one. It has to, in order to report accurately. If you have an issue that is in an active sprint…

Ah, yes, clone creates new issues in the same project the source issue is in. There are some apps that can provide "clone into another project" and "clone with edits to some fields" if you find you need to clone a lot.

Ok, there are two things to look at. Company-managed projects are configured with schemes. Two matter here: * The workflow scheme says "In this project, use this workflow for these types of issue, and use another for other types". The scheme has a default for any issue type you don't want to map to a workflow, but you…

Welcome to the Atlassian Community! The create button allows people to create issues in a project. The portal allows people to create requests, which leads to the creation of an issue as its back-end. You'll note that if you use the create button, you create an issue without a request in front of it. So there's a really…

I do not understand what you mean by "thread each issue differently". You still need to explain what the board configuration is for the backlog you are using, and what you have set up in the timeline.

Welcome to the Atlassian Community! Epics are expected to span sprints, because they're made up of many stories. But stories should not move between sprints. The whole point of a sprint is to deliver the stories that the team commits to doing in the sprint. If a story moves into the next sprint, the team has failed, and…

You can not, team-managed project boards do not support it.

Welcome to the Atlassian Community! Jira does not have a concept of sub-projects. The reason you are getting features created in the wrong project is that you are choosing to create them in the wrong project. I am guessing that you are not using the standard "create issue" button in the menu, which asks you which project…

Welcome to the Atlassian Community! Yes, that error message is wrong, it should say "you can not have more than 50 results". However, the cap on results is not a cap on the results from your filter, it's a limit on how much of the gadget is displayed. I am not sure what the limit does on the 2d gadget, but if you were to…

Hi Adria, The strategy has been "move to Cloud" for many years. New licences for new server installs stopped a few years ago, and for the last couple, existing licences stopped being alterable (you could not increase or decrease your user limits). Your options are: * Cloud * Data Center (lowest licence level is 500 users)…

Welcome to the Atlassian Community! What do you mean by "split"? What path do you want your people to follow and why do you not want to offer them the screens and workflow they want?