Nic Brough -Adaptavist- Expert

I am sorry, I do not understand the question. What is a "field ink to an issue type"? Do you mean "what fields does a particular issue type in a project have access to"? And I am completely lost on "add a configuration system for a system field" Could you explain the problem you are trying to solve maybe? 

Welcome to the Atlassian Community! You have to be an Agent in order to create issues (tasks) in a Service Management project. Customers can create Requests, which create an issue in the project (with a 1:1 relationship between them)

It shouldn't be a long list, that's why there's no simple "export list" function. You might want to take a look at the housekeeping and migration prep apps you can get - some of them make the list more manageable in the UI and a couple provide exports.

The hierarchy in Jira Software is Epic -> Issue -> Sub-task (noting that you can have many different types at the issue level and sub-task level - that's where you're seeing your Story and Task at the same level) Advanced Roadmaps extends upwards, and allows you to rename Epics, so if you're on Premium Cloud, you'll find…

This does not work, the whole server/DC suite has to be on the same type of licence. It can't work any other way - think about the apps and applications. JSW and JSM are applications that run on the "Jira platform". If you want to run a DC version of them, they have to be running on a DC licence for the platform. If you…

In some cases, you can go into project settings and change the type (only some conversions can be done, and you need to be an admin to do it). If the options for project type in there are greyed out, you'll need @Sebastian Krzewiński 's answer.

Welcome to the Atlassian Community! "Use Cases" are usually represented as an issue type in Jira. If you add the use case as an issue type to your projects, Advanced Roadmaps will happily work with them. Sub-tasks are a part of their parent issue, they don't have anything useful to say at a planning level, so Advanced…

Jira has a search built into it, which can report on everything, not limited by project. I'm not sure you really need a "data scraper"

Are you on Server or Cloud?

Welcome to the Atlassian Community! Could you explain what this has to do with Atlassian software? You have not mentioned any Atlassian stuff in your question, nor explained your acronyms and codes, so we are very stuck here. I am going to guess that you were reading a documentation site that was hosted in Confluence and…

Welcome to the Atlassian Community! No, the answer is still "use custom fields", because the current assignee is always supposed to be the person currently responsible for the issue getting done. Multiple assignees do not work, you should never implement anything like that. The whole point of the assignee field is that it…

Welcome to the Atlassian Community! All sprints are scrum artifacts, by definition, so I am not sure what you mean by "sprint that is not a scrum" You can document almost anything you want from your Jira issues in Confluence, by drawing in the Jira gadgets and using the Jira macro. So yes, you can log everything you close…

It can't do that, Jira doesn't really have a concept of "user selected by something". The closest you can get is "current user", which would be yourself.

Welcome to the Atlassian Community! In the project settings, you can set up an automatic assignee, but it is done in two places! First, go into the main "project details" and look at the bottom of the page - there is a default assignee option there where you can set "unassigned" or "project lead" (the project lead is…

Yes, it really is just the comment's existence. Other actions don't make you a commenter! If you have someone who has been assigned to the issue, edited it and transitioned it, but not made a comment (either by hitting comment or by adding one while editing/assigning/transitioning etc), then they will not be counted as a…

There are two points here - the preview and how the macro works. First, a lot of macros need real data to work with for the preview. If you've not got anything on the page before creating the table of content macro, it can't show you a preview. Try editing an existing page with content data already on it and then start…

Welcome to the Atlassian Community! * Watchers are people who add themselves to a watch list for the issue (or someone adds them). * Commentedby looks at who has made comments on the issue. A watcher does not have to have made a comment to be a watcher, and a commenter does not have to be a watcher The two searches are…

The columns are sorted by whatever you have in your board filter. Swimlanes are imposed later, and are in a fixed order, but within them, the issues in the columns remain ordered by the board filter settings. Please note that if you do decide to sort by priority, you will lose the ability to rank the backlog or board.

You can actually modify a simplified workflow and add screens and validators. But you could easily lose some or all of your customisations if one of your board admins decides to change the workflow. So I would net recommend modifying a simplified workflow. As Chris says, de-simplify first, then edit a standard workflow.

Ok, so basically, you're saying you are not working in an Agile way. That's fine, but you shouldn't be expecting an Agile tool to support non-Agile working practice.

You'll need to read the application logs to find out what the underlying error is.

See the issue linked to in the original answers

The only way to "fix" this is to stop using four different accounts

The hierarchy in Advanced Roadmaps is for the levels of Epic and above. It does not change the standard Epic -> Issue -> sub-task in Jira Software. All you can do here is make your "task" issue type into a sub-task type, where it will work alongside (not above or below) the existing sub-task type.

I would re-check the firewall - connection refused is a typical response from a firewall block.

No, the project board in JWM remains in place.

Welcome to the Atlassian Community! I'm sorry, but your question does not make sense. I think "club all together" means you want to report that shows issues of all three types together in one place, but I don't understand what you mean by "bucket" or "remove from my issue status" Then in your question you say you only want…

Yep, team-managed projects aren't really ready for serious use yet.

Could you explain what you expect a sub-project to do? We may be able to show you how to configure projects to do what you need,

You'll get this when the creator of an Epic has left the name field blank, or an admin has removed the field from the Epic create screen. The field lock is not preventing you correcting this, the lock is actually preventing you making worse mis-configurations like making the field optional or applying it to non-Epic issue…