Vignesh Jayagopal Rising Star

Hi @Gemma Huang I can see that you have configured the "Business VP Approver" field in the workflow. Could you please confirm whether this field has also been added to the request type and the issue screen? I assume this is a User Picker field. If so, the approver needs to be selected through this field when the request is…

Hi @xxx69 Welcome to the community! To add a new status to your workflow: Select the relevant form of status. Eg: Click on the In Progress status. Enter your desired status name to add it. Refer to this link for more details on team-managed project workflows:…

@Marc -Devoteam- Yes, that's correct. The above is only applicable in Paid plan.

Hi @Ruslan Tsybulka Welcome to the community! You can update your instance URL by navigating to:Admin Console → Products → Product URLs → Select "Update URL" for the respective site. Please note that the URL can only be changed up to 3 times per instance.

Hi @vaughan.dickson Try removing the user from all project roles and group memberships related to Jira and project permissions. If the user was previously assigned to any issues, their name might still appear in historical comments or mentions, but they should no longer be taggable in new comments once their access is…

Hi @Kevin Vancrutsen You need to have the same workflow for both Incident and Service Request. Then, in your automation action, update the Issue Type and Request Type accordingly. We had a similar use case and configured the rule action as shown below.

Hello @Lucas Linzmeier Subtasks can only be created as child issues under existing issues. They cannot be created using the "Create" button at the top.

Hi @Sachin Guttala You can achieve this in the Request type configurations. Navigate to your JSM project settings. Under Request Types, Select the request type you want to update, remove the custom field from the Request Form so customers can't see it. Keep it in the Issue View to ensure agents can access it.

Hi @Lars Löhner Welcome to the Community. To restrict project visibility, you need to add the appropriate role or group in your project’s "Browse Project" permission. This ensures that only authorized users can view the project, while others won’t have access. Kindly refer to the article below for more details.…

Hi @Rob Cadwallader Welcome to the community. In JSM, users don’t need to be verified/managed to receive email notifications. External users also receive notifications through Customer Notifications. If you allow users to be created as external, they may be created as Portal-only customers rather than Atlassian accounts.…

@Josh Noren We are also experiencing a similar issue in our organization. When I was checking, I couldn't find a solution and found that there is an open feature request with Atlassian regarding this. https://jira.atlassian.com/browse/ID-6403 

@Kyra Stewart This is the Atlassian Community, and any details you post here will be visible to all community members. Please avoid sharing sensitive informations here. If you need to contact an Atlassian Technical Support member, use the link below: https://support.atlassian.com/ 

@Chuck Oleary You can see all your custom fields in the admin Section, Issues--> Custom Field. You can also get it using the below API endpoint. GET https://your-domain.atlassian.net/rest/api/3/field

@Osama Al-Areky Kindly accept the answer if it helped you, so it can benefit others as well.

@Ferry Portier Yes you can create your custom field and simply add your existing group in the filtering section.

@Carsten Fries Hansen You can achieve this using workflow conditions. Configure the transition in the workflow by adding one of the relevant conditions below. This will ensure that only specific users can perform the transition. Simply exclude the PO from this condition, which will restrict them from changing the status to…

@Ferry Portier You can create a "User Picker (Single)" custom field in Jira and set up a group with your project members. Then, in the custom field settings, use the User Filtering option to restrict selection to members of that group.

@Osama Al-Areky I could see the fields are visible when you view the issue as per your screenshots. Please clarify which screen you are referring.

@Osama Al-Areky From your screenshots shared, i could see the Start Date & Due date under the Description field. What is the issue here? you want to move those fields to the right side panel "Context Fields" section?

@Yury Ked This should be working, Please reach out to Atlassian support to check what is missed here.

@Yury Ked No need to remove the Reporter from the permission. It's strange—I have the same setup, and it's working fine for me. Are you testing with the issue status set to In Progress? This restriction only applies when the issue is in the In Progress state as you have added the property in that status, and the Reporter…

@Yury Ked It worked well for us, need to spend some time on this to see why this is failing for you. Can you try deleting the jira.permission.scheduleissue.reporter property and keep only the two properties for Lead and Administrators? This way, only the Lead and Administrators will have permission to edit the due date,…

@Glen Brannigan Kindly mark my answer as accepted if that helps. For your second question, you can try like below.

Hi @Glen Brannigan You can try setting up the rule like below.

@Yury Ked Could you try deleting the property for the reporter and test again? Also, please ensure that the reporter is not assigned an admin role or set as the project lead.

Hi @Yury Ked We had a similar requirement, and instead of removing the field from the edit screen, we restricted editing using status properties. This approach worked well for us. You can try the same and refer to this detailed overview on status properties in the link below.…

@TechSangam Kindly mark the answer as Accepted if this has helped you, so that it will be useful for others as well.

Hi @testing1 You are trying to add a new field to the screen, for that you need the "Manage Issue Layouts" permission. With the "Administer Projects" permission, you can still edit the layout by rearranging existing fields, changing their order, or moving fields between the Description section and Context field section.…

@Dave Mathijs Yes, users with Administer Project permission can edit the issue layout. However, I don't believe they were previously able to edit workflows, as only users with Jira Administrator permission have the ability to modify workflows.

Hi @TechSangam @Dave Mathijs The "Manage Issue Layouts" permission was recently introduced by Atlassian. Previously, this was inherited under the "Administer Projects" permission. So, users with the "Administer Projects" permission can still edit the issue layout. However, a suggestion has been raised to Atlassian to…