Generally the answer is no, this setting is at the system level only. There may be an addon that could accomplish what you want, I found one candidate but I have not used it personally. https://marketplace.atlassian.com/plugins/com.metainf.jira.plugin.emailissue
The first question is a problem that many people have issues with. Each successive email response adds more and more to the bottom of the message. This is more of an issue with the email server and its configuration than JIRA. Turn off the feature where it dumps the entire thread into responses to JIRA.
From the Atlassian Documentation: For each event notification, JIRA will only send the first encountered email intended for a recipient. Hence, in the case where a user is included in two or more recipient lists (e.g. the Project Lead and current reporter) for one event notification, the user will only receive the first encountered email […]
The easy answer is that Atlassian needs to protect the integrity of their system. Workflows cannot simply be imported, they are part of a bigger setup. Custom fields, screens, and issue types all come along with a workflow. It is possible to import workflows into JIRA Server, this can be done by an experienced administrator.
Regarding the pop-up you are seeing, please try to use as username only “admin” and use the same password you have for the administrator of the cloud instance.
JIRA fields, columns on agile boards, screens, and issue types are all customizable. I encourage companies to use terms that mean something to the team vs using blanket terminology. The easiest example is a “stand up meeting” instead of a “scrum”. Most people do not understand the word scrum outside of rugby so it makes […]
Too many fields in a system can impact performance so you want to be careful. Generally it is very important to limit fields in issue types to those fields that are useful. The goal is to make it easier on the user to complete their work. Our basic rule is to use one field for […]
Ironically the two boards end up being the same with the same options. The difference is that the Scrum board adds a layer of organization and planning in front of the eventual board. If you want to simply display issues and organize them, use Kanban. If you are planning sprints, use Scrum.
We have found that creating an issue type to specifically track an initiative, or a major feature to be the most effective. You add all the needed fields to flesh out required reporting in this “Project Management” issue type and keep the burden away from the development team.
In the workflow you need to modify the transition. Highlight the transition when in edit mode and edit the options for the transition.