Mikael Sandberg Community Champion

Hi @S_ Morgan, Welcome to Atlassian Community! You are better off asking your Jira admin that question, those fields are custom fields and your admin should know the process around them. The community do not have access to other customers instances. 

Hi @Luis Collado Did you use the Performance review template? Note that this template creates a Work Management project and would therefore not be available from the Help Center. Users would only be able to submit issues if they have access to the project, either via the Create button or via a form that you can create and…

If your team's tickets are across multiple projects and you want to stay with your team-managed project then your options are limited. You could create a filter that shows all the issues, or you could use an app like Structure or JXL. The best option would be to move to a company-managed project, because then you will be…

Hi @Aymane jilali, Welcome to Atlassian Community! It is not possible in the request form, but you could use Forms and make a conditional section for each request. The first question on the form would be what the request is about, and then if the user picks laptop and access both of those sections would be displayed. You…

Hi @Jean Geraldine Gatus, Welcome to Atlassian Community! No, team-managed boards cannot be configured to include issues from other projects, it can only show issues within the project. It is only work-managed projects/boards that can show issues from other projects since the board has a filter associated with it that can…

That is from the vendor, Atlassian has a privacy and security questionnaire that the vendor can fill out and this what is being used for the Marketplace listing.

If you check the Marketplace listing for the app and the Privacy & Security tab it is stated that the app does not process end-user data outside of the Atlassian product, so that would mean that the data stays within Jira.

Yes, you can do this with automation and in its simplicity the automation would look something like this:

Hi @Brian Goodson, Welcome to Atlassian Community! Yes, it is possible to add users as collaborators in a JSM project. The requirement is that those users have a Jira license assigned to them. They will be able to view requests and add internal notes, nothing else. You can learn more about the roles in JSM in this KB. 

As @Joe Pitt mentioned apps works for all users unless the app has user control which very few of them do. Xray does not have user control, you can only control which projects should have access to it.

If they are only being displayed on the portal then go to the Request form tab and remove them from there. Any field that is listed on the request form will automatically be listed on the issue view.

Hi @Kalen Peredo, Welcome to Atlassian Community! If you go into the request type and the Issue view tab you can remove the fields you do not want to see by dragging them from the middle to the right hand side. Once you are done doing this, just save your changes. 

Are you sending a link to a specific space? If so, check to see if that specific page has restrictions. Even if a user have access to the space they may not have access to the page if view restrictions are used. Also note that view restrictions are inherited down from the parent, so even if the page in question do not have…

Hi @Karl Reading, Welcome to Atlassian Community! The way your query is currently configured it will return Triage issues in the specified projects with label A, or return any issues with label B or C or D. When you are using OR in a query it is important to also use (), otherwise the query will behave differently than…

Hi @Ron Rogers, Welcome to Atlassian community! Yes, that is possible, and you do that by adding an override. You can choose to add another user as the override, or if you type in No one you basically remove that user from the schedule during the time you have selected. You can learn more about the override in this KB. 

Okay, so you can set the initial update in two (or three if you count PATCH and PUT) via the API. You can do it either via Create an incident, or via the Update incident. The body is not a required field so you just have to pick which option you like better. Then when you add a new update you will use Incident Updates.

That is the thing about linking the form fields to Jira fields, you will see duplication of data. In the projects that I have that are using forms, in most cases I am not linking the form fields to Jira fields. The only case were I do link the fields is when I need an automation to trigger on changes to fields, or if I…

Hi @Kalen Peredo, Welcome to Atlassian Community! In this case the best way of doing this is to create a form that has conditional sections based on what the user selected on a previous question. You can learn more about Forms here.

You could do this if you trigger the SLA to start when the due date is set, the only thing is that you would have to cover the amount of time between now and the due date in your goals. At most you could only cover due dates that are 90 days out or less, since the SLA can only have 90 goals. So if the due date was lets say…

Hi @Reddy Girish, Welcome to Atlassian Community! What you see is expected, the issue is only holding the asset key as a reference in the custom field, so you would have to use the API for Assets in order to get the value you are looking for.

Hi @Stuart Murdock, Welcome to Atlassian Community! The short answer is no, it is not possible to use wildcard when searching labels. In order for that to work you would need an app that extends JQL to allow wildcard search. I know Enhanced search for Jira/Scriptrunner is able to do this, but I but one of the other apps in…

So there are two ways to create the initial update of an incident, either via Patch or Put. But the payload is the same for both. And if you look at the description of the body that is for the initial incident update. This is the important part: The initial message, created as the first incident update. After you have…

The body is not replacing the initial message in the incident, the body in the update incident will set the first incident update message, and then if you need to add more updated you will use Incident Updates to do that. 

I know JXL can show you the structure and we use that for reporting. Not sure about integration with Confluence besides Analytics, which you get access to if you are on an Enterprise plan, which can be used in Confluence using smart links.

Hi JiraLearner, Welcome to Atlassian Community! In order to set up the hierarchy you have to go to either Settings > Products > Hierarchy configurations or Plans > Settings > Hierarchy configurations. Both of these paths will take you to the same page were you can set the hierarchy. Please note that you can only configure…

The short answer is yes, you can add multiple issue types on the same level. For example in my instance we have three different issue types on both the Theme level and the Epic level.

Business days are considered to be Monday to Friday, 9am to 6pm, so it all depends on when on the Oct 11 the request is created, if was before 9am the due date would be Oct 14, otherwise Oct 15.

Hi @William Strickland, Welcome to Atlassian Community! What you see is expected, the asset custom field will always return the object key when you are using {{issue.customfield_X}}. In order to get to the attribute you are looking for you have to use the dot notation, something like this, {{issue.customfield_X.Location}}.…

Hi Learner, Welcome to Atlassian Community! The calculation was correct, since Oct 12 was not a business day, it started counting on Monday, so two business days from Oct 12 would be Oct 15. For rules like that and the issue is created on a non business day it will start counting from Monday on.

Hi @Julie Lepage, Welcome to Atlassian Community! Check your workflow to see if the transition require that Parent is filled out and also check you field configuration to see if the field is set to required.