Comments
-
Welcome @zoe.baldwin Yes you can, since it will be removed from the database and then re-added to the database (I know this is a cloud version).
-
Welcome @Gabriela Pan The thing with the lists is that each user is setting the list view according to their needs. So yes, currently you would have to guide the users how to set up the fields in order to see them. I would recommend writing a Confluence page about this and link it to your Jira project so it saves you time.…
-
Hello @Eric Roetenberg Not sure what do you mean by switching from EPIC to FEATURE? Are you using FEATURE issue type instead of an EPIC? There is an issue hierarchy that defines which issue types can be associated with the Epic level, which is level 1. More:…
-
Welcome @dan murray Which documentation you have been using? Can you give more details which part doesn't work for deploying?
-
Hi @Sathya No, this cannot be hidden as this was hard coded by Atlassian to work in this way for an easier navigation between the pages.
-
Welcome @Barry Hueston Usually when the text is purple like that by default, this could be a link. Also are they using light or dark theme?
-
Hi @Barbora Kutikova You might want to check this article: https://community.atlassian.com/t5/Confluence-questions/KB-Only-visible-to-Confluence-Users/qaq-p/2876628
-
Hi @Peter Melichar FJD Jira doesnt have this functionality, but it's under the Atlassian's consideration. More information could be found here: https://confluence.atlassian.com/jirakb/how-to-change-jira-service-management-customer-email-address-1085190839.html
-
Welcome @Aarushi Saraswat Try clearing the cache and start with the incognito mode as well.
-
Hi @Peter Melichar FJD Since you are saying that you cannot delete profiles and change the email addresses, this is because you are not an organization admin. Only org admins can manage users and in this case their email addresses as well. Instead of removing accounts, best practice is to deactivate their accounts. All of…
-
@AGSuite Technologies You have to click on the project settings (the cog icon): This is from the example project.
-
Ok, when you go to Project Settings, do you see Issues or Issue types?
-
Hi @Amulya Sankara One of the ways you can actually do this is bulk transition and moving issues to the next sprint: * Issues > JQL <span>Query: status in ("Code Review", "Acceptance", "Test Env") AND Sprint in openSprints()</span>Then you select three dots and select Bulk Change.You would then select Transition issues to…
-
Task has its own unique issue type id regardless if the issue has been created or not. If this is a team managed project, you can find it under Project Settings > Issue Types > Task If this is company managed project, you can find it under Project Settings > Issues > Types > Click on the Task issue type and it will…
-
Hi @AGSuite Technologies Like the error says you need to provide the key of your parent issue, which is task and with this payload I don't see the the ID of your issue type. You can find this when you go to Issue type scheme of your project and click on the issue type. Within the URL, you will see the ID.
-
Welcome @AGSuite Technologies * What error are you facing? * Have you tried with webhooks? * Have you tried some integrations with Zoho from Atlassian marketplace?
-
Welcome @Alice Black Is this happening every time? If yes, then there is an either project or global automation rule where you are set to be the assignee. First check those. Then if not, you can change the value of the Assignee field to either Unassigned or someone else - you need to have the Assignable user project…
-
Welcome @Oliver Haag This is not supported by Jira, but the part that you mentioned about the ordering is actually the ranking of the issues on the board, where you can drag and drop issues either below or above one another. For this you also need to have schedule and edit issues permission.
-
@Francisco Zarabozo It makes sense only to view the workspaces you own,otherwise it would be a security issue.
-
Welcome @Francisco Zarabozo You can try with https://developer.atlassian.com/cloud/bitbucket/rest/api-group-workspaces/#api-group-workspaces But from this documentation there isn't a mentioning about retrieving the email address.
-
Welcome @Kiran Kumar Bussa You can only assign issues to individual users. You can also include the Team custom field to your screen, since this is a team-managed you can do this through Project settings > Issue types. From there you search for Team field and add it to the issue type. More about Teams in Jira could be…
-
@Volker M_ Another way you can do this is with your permissions which are Create issues and Add comments. For create issue permission for the users that you that want to be able to do this, you can create a new project role which will be excluded from that permission but you will assign that role for the users. And then…
-
Hi @Volker M_ Do you have transitions applied to your workflo? Either statuses with All transition or the transition from one status to the another? You can apply a condition of User in a project role and for the project role you either choose service desk team (agent) or the customer. Next you would need to add a property…
-
To view these issues, you would click on the Search bar of your navigation, then click on the View all issues, select the JQL and then copy and paste the query that I have sent from above.
-
Hello @Michelle Flanagan Clear your cache and try with the incognito mode.
-
Kindly accept the answer so others can refer to it.
-
Welcome @Jenn Hertz JSM projects do not support roadmaps, only software projects.
-
They can see the replies without having Jira account but the option from the screen shot needs to be enabled.
-
Welcome @Mika Steyn First, you need to make sure that your portal can be accessed without the need to have the Atlassian account, but this will affect all of the JSM projects created. You need to select Allow customers to create accounts and Customers can access and send requests from the portal without logging in. Then,…
-
Done column needs to be the most right column.