Florian Bonniec Community Champion

Hi @Brittany I do not have access to a JSM Cloud instance for now but it seems that what you are looking for is documented here https://jira.atlassian.com/browse/JSDCLOUD-349 Have a look to the "Updated 20 December 2022" note. I also do not recommand to use the workaround that was listed. Removing the request type will…

Hi @Matthew Lee Not 100% sure but I think it will update the way it's displayed but data is stroed in sec so if you logged 1d before the change it will not update from 6 to 8 but it will be displayed 6h istead 1d now. When you will log 1d it will log 8h for the new work log entries Regards

Hi @Daphne Wallen For completed task you can use a JQL on resolutionDate. resolved >= startofMonth("-1") and resolved < startofMonth() For In Progress stuff you can use operator was and issue not resolve. status was "In Progress" DURING ("2010/01/01","2011/01/01") and resolution is empty…

Hi @Aurélie Pilette I would say that the folowing JQL then displaying it in List View with "Parent" field as column should contains issue with sub-tasks != Done. parent is not empty and status != Done Regards

Hi @Josh Flori Parent link has never been working for searching using JQL. Hope this ticket will help you to understand why https://jira.atlassian.com/browse/JPOSERVER-2477 Parent Link is not EMPTY considers 3 types of "parent links": Parent Link from Portfolio, Epics and subtasks. To search issues with only the Parent…

Not sure about the link name but it can be found in the db using this query select * from issuelinktype where pstyle is not null It's one of the link listed. Regards

In you script you seem to clear some link maybe you are cleaning the one that is created between sub-task and task ? Even if not displayed in Issue Linking JIRA use links between those issues. Link should be Parent-Child Link. Regards

I've already seen orphan sub-task like that but never spent time to investigate as it's quite rare. Everytime it happen my users told me that it was during an automation rule execution when they was creating sub-task from the story creation using automation but deleting the story before it ends. It's not the steps you…

Hi, I don't think this is possible as Advanced roadmap is meant to help you plan across your organization where team managed projects are meant to only be managed at the project level without interaction with the others project. https://jira.atlassian.com/browse/JSWCLOUD-20012 Regards 

Hi @JD Lobue It's the purpose of customer for JIRA Service Management, they do not consume any license but have only customer portal access. https://support.atlassian.com/jira-service-management-cloud/docs/what-are-service-project-customers-and-organizations/ Regards

Hi @Rob_van_Maanenberg Are you using JIRA Cloud or Data Center, do you have apps such as Scriptrunner or JQL Tricks ? Regards

Hi @Glenn Simpson On cloud it will depends if you project is a Team managed one or more classic. https://support.atlassian.com/jira-software-cloud/docs/customize-an-issues-fields-in-team-managed-projects/ You will be able to edit the avaialble option if it's a team managed project but would need to ask a jira admin in case…

Are you in the Behaviour section of Scriptrunner ? You need to define if so it will be something like that def formField = getFieldById(....)

Hi @Mohamed Saad Taha Yes you should be able to. You have to set the Cardinality of the attribute to 1 https://confluence.atlassian.com/servicemanagementserver/adding-attributes-to-object-types-1044784524.html Regards

Hi Sometimes you have to try couple of times. Also have you check the log when updating the app to see what the error is ? Reagrds

Hi @Dora Judith Martínez Vera It seems that the listener on value change is done only at creation, you can add edit in the configuration of the trigger in "Para" no ? Note that if you add a value or remove it will re-run the entire automation. You will porbably need to add if then else condition to avoid multiple issue to…

Yes it's was just an example, you have to adapt using the field id of the field you want to set the error under.

Hi @Alex Hoogendoorn You can ask your JIRA admin to review the Workflow use for the specific issue type in the project. Most likely there is a postfunction that clear the Sprint field when transitioning from one status to another. https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/78480000/Clear+fields Regards

Hi @Alexander Lukyanov The current version of Xray you are using is not compatible with JIRA 9.5.0, you need to update Xray to 6.3.0-j9 at least. Regards

Hi @Adam LaCoste There is no way to prevent that if you have all type within the same porject. You could create your Epic within another project and do not grant Work on Issue to anyone in this project. Otherwise you can have all type in the same project but use a script fragment from script runner if you have this app to…

Hi @Nannette Mori First this function apply to Behaviour script only. formField.setError means that you have define formField before with something like formField = getFieldById("customfield_11111") https://docs.adaptavist.com/sr4js/latest/features/behaviours/api-quick-reference Regards

Hi @Vara Prasad You can ask the JIRA Admin of your company to update Advanced Roadmap Configuration in order to add more link as Dependecies. https://confluence.atlassian.com/jirasoftwareserver/configure-your-jira-software-instance-for-advanced-roadmaps-1044784156.html Please refer to "Configure Dependencies in Jira for…

Right it's the way to go if you want to have the information per project. Note that actually Service Desk role do not grant any permission. In fact all agents from a project are all users having the Service Desk Agent permission (permission scheme of the project) and have the application access to JIRA Service Desk…

Hi @Marcos Strapazon First you have to make sure to use the right rest api doc, if you are on server you have to use the server api not the cloud one. You can go to the admin section > Application > Application Access then get the name of the group that grant agent permission. Then use the api to get the list of user of…

Hi @jmacbean-pandora All Epics the user is able to see will be displayed. You can reduce the list of epics by changing the Epic status to removed Done Epics by defaut (Epic status is not the same as the status from the workflow, it's a field). Also you can reduce the amount of Epics displayed by managing permissions to…

https://jira.atlassian.com/browse/JSWCLOUD-21897

That means your issue do not match the rule you set, someone may have updated the issue since you transitionned the issue to the last column. Regards

Hi @Gile Empey What do you have configured under the Kanban config (Hide completed issues older than)?

Hi @Karyn Smyth No it will remain as long as you decide to archive or delete it. Regards

You can vote for this suggestion https://jira.atlassian.com/browse/JSWCLOUD-19762