Comments
-
Hi Simon! Well, that's not something you see every day. Are you still able to edit the issue layout from project settings -> Request Management -> Request Type? If you can, it might be a bug related to the new UI. If you cannot, you are probably missing the "Edit issue layout" permissions. Regards, Jaime
-
Yeah! That's what i meant. You will have to "suspend" the user access. The user won't have access to your organization but they will remain in the directory, so they'll still show up in the field. Hope that helps! If so, would you be so kind as to accept the answer so it can help others in the future? Regards, Jaime
-
Hi @Rhett Reeves ! Welcome to the community! What Trudy answered is completely correct. I just wanted to add that you could also make use of ROVO for this situation. In automation you would use the "Use Rovo Agent" and in the prompt you could indicate the Confluence page you want to copy from and then use the smartvalue…
-
Hi @Evelyn Lewis ! Glad to have you in the community. In automation you can make use of Smart Values to verify the lenghth of your description before executing the rest of your automation. In this example, we would be using the smartvalue {{issue.description.length}}, which you can learn more about here-> Java…
-
Hi Venkat! Others have already given you details on the difference. I only wanted to address your question directly. Yeah, the user will still show up. Have a lovely day!
-
Adding to what @Johannes Wiedmann mentions about queues: There is a big inconsistency on how a user accesses a Business project and a JSM project. You can go to a business project by clicking on the project name, yet clicking on the JSM project will open what used to be the sidebar menu. If you want to go to a queue you…
-
Hi @Venkata Sagar Ganesh Rao Mahendrakar Sadly changing the renderer to the wiki style will change your field to use the Confluence interface, which does not support font size modification. Only by using the headers available can the font size change. Regards, Jaime
-
Good dary Erik! So the big one here is probably ROVO. It can access all of your instance data so that should help tap into the knowledge of your organization. It can, for example, propose tests out of a functional design. Combined with automation, you should be able to create a batery of tests. Xray Test Management for…
-
Hi Venkata! Welcome to the community! I'm afraid there is no option to modify the font size in any field 😣 The only workaround here would be changing your browser's zoom level. Regards, Jaime Escribano
-
Good Morning Joshua 😊 Could you share a screenshot of the approval configuration and an example of a ticket where the users are not showing up? In my experience, these changes happen right away so there probably is some error with the configuration. Regards, Jaime Escribano
-
Hi Pieter! Welcome to the community 😊 I can see the template suggests using /Jira to include issues. This macro is not really suited to create new issues in Jira, just displaying. If you want to have the page dinamically update the sub-tasks of a given epic, you can use the /Jira issues macro to filter by JQL as in this…
-
I fully agree on the information overload front. Having used it for a few days i've gotten over some of the basic pet peeves, yet I often become overwhelmed if I navigate through a filter, a project and later on look at dashboards. I feel like i need to click to hide elements constantly. The Filters tab is the worst…
-
Hi Niklas. I apologize for the confusion! I read your automation wrong. The logic you are actually using is "If the status from the parent is not the same as the sub-task and those sub-tasks all match the status of the sub-task that triggered the issue". So I would go back to my first idea: The transition you are trying to…
-
Hi Nikklas! The problem here is that your PARENT status cannot transition to the status of your sub-tasks. That may be becouse your parent issue is not at the status you expected or becouse there is a condition that is not satisfied :) I could recommend adding an "all status can transition" to your desired status and…
-
Hi Antonia! Let me try to break it down to you: "Directory": Shows all the Customers that have interacted with your Jira Servicemanagement Project, so users that have access permissions. These may or may not be Atlassian Accounts (portal-only accounts are different to the ones we are using, for example, to make questions…
-
Hi K! We get this question a lot :) To add a logo to Confluence pages, you can either change the site logo in Confluence's general settings or add a header image to individual pages. The site logo appears in the header for all pages. Header images appear above the page title on specific pages.…
-
Hi Preethi! Welcome to the community! There is an API endpoint to fetch your customers for a given servicedesk: Fetch Customers - Atlassian API In orther to find out what your servicedeskID is you will probably want to use this other endpoint first: Get Servicedesks - Atlassian API Finally you can find this info via UI by…
-
Good morning Debanjan! Welcome to the community! When modifying the status you should be able to see all posible status changes that a ticket can go through. I imagine your problem is that no statuses are available as the workflow was designed for that status to be the final one. If you can see statuses, you can go through…
-
Good morning Vitheya! Hope you enjoyed your weekend. Before I look into this, would you share what the failure is? API Error, result is not the same as expected, some other issue? Regards, Jaime
-
Hi Sara, happy to welcome you to the comunity! The reason why they are created that way is that you have a status mapped to the kanban backlog which is probaly the initial status for your newly created issues. Therefore you have two sollutions: * Remove the status from the kanban backlog and map it to a new column. This…
-
Hi Denis. Welcome to the community! Would you mind re-uploading the screenshot? Im afraid we can't see it
-
Hi Favian! I see you liked my response. Would you mind marking it as an accepted answer so that it can help other users in the future? Many thanks!
-
Good morning Vincent! Welcome to the community! There is an easy way to find out if the accentuation is affecting your automation. Could you try out changing the smartvalue from {{lookupIssues.Story Points Renée}} to {{lookupIssues.customfield_XXXX}} where XXXX is the ID of your custom field. That way we can discard any…
-
Good Morning Vitheya! I can see in this code snipet const globalContext = contextData.values.find(ctx => ctx.isGlobalContext); that you chose the global context of the field, which is the reason why it shows up in all projects. You would need to define a new context for each set of projects you want your field to have…
-
Hi Preethi, wellcome to the community! It would depend on what the details of this customer are. Details such as the e-mail or display name are displayed in tickets, not really stored in them, so you would see the newly changed data no problem. Different information wouldn't update so easily. You mention that you have some…
-
Hi Fabian! Hope you are having a lovely day. Sadly, I have been looking over the documentation, and I'm pretty sure what you are trying to do is impossible. You could achieve the functionality with plugins such as ScriptRunner or JQL Search Extensions for Jira | Atlassian Marketplace Regards, Jaime Escribano
-
Hi Richard! Could we get a screen capture of your attempt? You seem to be using a Jira Expression which is something that I didn't know you could to in Automation :O The behaviour you are trying to accomplish could be achieved using workflow plugins such as Workflow Magic Box | Atlassian Marketplace (disclosure: My company…
-
No worries! I can see where the confusion is coming from. {{issue.customfield_18631}} ~ {{LookupOrder}} AND parent = 'ACMEINC-104' here just write the name of your customfield. For example if the custom field was "description" the JQL would be: description = {{LookupOrder}} AND parent = 'ACMEINC-104' If you notice,…
-
Hi Patrick! Glad to see you reached out to the community! Your options would be: Manual Move : Jira admins can move issues between projects by editing the issue and using the "Move" function. During the move, you'll need to reassign the request type and map any fields that don't align. This is not super recommended as it's…
-
Hi Alicia! Hope you are having a lovely day. I think you are looking at the wrong menu. You should be looking at the Board settings, not the project's! In the new interface, you can check it out here -> At the top right in the older interface you should be able to see the same menu if you are a board administrator :)