Alexey Matveev Expert

Ok. I now understand the problem. If you create an issue by the + sign, you choose the correct issue type (not request type), that is why you should manually set the request type. When you use Jira Service Desk, you are supposed to create tickets either via protal or email. In the Jira interface Agents process issues,…

Hello, Could you attach a screenshot with the plus on the far left hand side? Or give more details where is the screen.

Hello, You would need to change project notification schemes in your Jira Cloud. You should exclude this user from any groups, roles, which are defined in the project notification schemes. You could find more info here: https://confluence.atlassian.com/adminjiracloud/creating-a-notification-scheme-776636401.html

Hello, If you want to update your Jira Software 7.12, you should do it according to this guide: https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html

Hello, You should add the Work Bucket Type to the create screen, or go to the project field configuration (project settings -> fields) and set the Work Bucket Type as not required.

Hello, You need to add this user as participant to all issues, which must be visible for this user.

It will not solve your problem. Issues belong to a project, not to a board. As long as you choose issues from the same project, you will not be able to work with them as separate issues on different boards.

@Stuart Tiedeman You can not use the version feature of classic projects in next-gen projects yet. Maybe this feature will be available in future releases. Right now you should stay with classic projects, if you want the version feature.

Hello, Kindly make sure that the fixVersions field is defined on the create screen for the Story issue type in the ZEM project.

Hello, Click the three dots and choose more actions, then enter your status there and choose the transition:

Hello, Try the following line in your JQL: Approvals = approver("username")

Hello, Go to project settings -> workflows. Find the workflow, defined for the required issue type, and have a look at the validators, which are defined for the transition, you use. Maybe there is something unusual.

Hello, Boards do not contain issues. Boards just represent issues from projects. That is why if you modify an issue from a project on one board, it will change on the other board. One issue can have only one status in a certain time.

Sorry, I do not understand what you are trying to do. What is a Wallboard policy?

You are welcome! If my answer helped you, kindly accept my answer.

You can add a tab to a screen and control the order of fields, but you can not make a field appear, for example, under the attachment web panel. If you want to control the visibility of a field dynamically (let's say to show or hide, if another field is filled with a certain text), then you would need a plugin.

Hello, You can create a new issue type scheme with the required default issue type and assign this issue type scheme to this project.

Hello, Go to project settings -> details and change the project type from Business to Software.

Hello, You can not group swimlanes by two entities. 

Hello, When you add this post function you have a field to enter the value for your custom field. Enter there the name of the required user.

Hello, Unfortunately, you can not search with a wildcard in the beginning of the word out of the box. You would need an add-on for it.

Do you mean that if you Select the Permissions option, then you can not see the current permission scheme?

Hello, Are you on Cloud or Server? if on Cloud, then I guess you created a next-gen project. This project type does not have the permissions menu option. And you can not change permissions.

It means that the Story point field is not on the subtask screen. Go to project settings -> screens. Find the create screen for the subtask issue type and add the Story Points field there.

Hello, You should move your ticket to the most right column.

Hello, You can not add a select field right now to a next-gen project. But it is in the Roadmap. We will have this feature in future releases.

You can not control the placement of some system fields like summary, description, resolution, status and so on. You can control the order of custom fields and add tabs to screens. Basically, it is the same in all 7x versions.

Hello, You can set the from field in the email per project. You can find more info here: https://confluence.atlassian.com/adminjiracloud/configuring-email-notifications-776636790.html

Your question is too abstract. I can answer this way, there are not changes in handling Jira screen UI from 7.0

You are welcome!