Florian Bonniec Community Champion

Hi Not sure if it's the rendering or not but quote (") do not have to be added it's just jira.issue.editable Also did you set the property on the status <span>HR Approver team</span> or the transition to it ? You have to set it on the status. Regards

Hi @thumuluru.shreya You can do it from Atlassian directly. Everything is explained on the Atlassian page. Professional Certifications : Atlassian Regards

Hi @Kemal Solmaz If Found in version is a single select version picker. You need to push only 1 value to the field. But Affects Version is a multi version picker. You could use smart value on the edit field directly and not use the Advanced edit with json. Smart value could be {{issue.versions.last}} Regards

Hi @kapild Are you sure the user you are using have permission on the "IT Access Management" project ? Regards

Hi @wasin wakton Are you importing from a file ? It's seems that you have CASE Sensitive issue. Replacing set by SET shoudl worked no ? Regards

HI @[deleted] You have to create a new board if you want to change board type. If you are using Team managed project, you can turn on/off sprint. https://support.atlassian.com/jira-software-cloud/docs/enable-sprints/ Regards

Hi @Yash Khandelwal 1- You have to make sure Reporter has the browse project permission as well as any other permission it may need, like edit transition. It's configure in the Permission Scheme. https://confluence.atlassian.com/jirasoftwareserver/permissions-overview-939938996.html 2- You need to set a workflow property…

Hi @saravanan subramanian Because you are using the assignation endpoint and not edit endpoint you do not have to specify the field to update. Payload should be like this const bodyData = `{ "accountId": "5b10ac8d82e05b22cc7d4ef5" }`;…

Hi @Ashok Shembde Could you update the notification scheme instead ? Configure notification schemes | Atlassian Support Regards

You just have to write it where Tigger Issue is wrote. It looks like it's a select list but in fact you can input whatever you want in it.

Hi @Ram Freedman You should be able to input the issue key directly instead of "Trigger Issue" Regards

Hi @Shraddha Patil You can find this information here: Storage Platform quotas and limits Platform quotas and limits Regards

You cannot apply different value when doing a bulk change. Only way is to have a transition with no screen limited to some group/role to not have it available to everyone. Regards

Hi @leonan_machado Welcome to the community. If it's something you have to do often, did you evaluate the possibility to add a transition without the screen limited to admins only ? Regards

If you have a look into the database directly, are you able to find the table ?

Hi @Andrew Thomas Based on Atlassian suggestion tracker it's implemented for JSM Cloud (https://jira.atlassian.com/browse/JSDCLOUD-133). This article from the community may help you. https://community.atlassian.com/t5/Jira-Service-Management-articles/Pre-populate-Fields-from-URL/ba-p/1997476 Regards

Hi @Keerthivasan It may be related to a validator configured in the transition you try to run. * Navigate to Workflows: * Go to the JIRA administration area by clicking on the gear icon. * Select Issues from the dropdown menu. * Click on Workflows. * Edit the Workflow: * Find the workflow you want to edit and click…

Bonjour, En Agilité, tu ne devrais pas compléter la Story si celle ci n'est pas fini à 100% car il n'y a pas de valeur créé. Si tu peux divisé la Story en 4 puis 1 point, celle ci a probablement été mal définie à l'origine. Une solution pourrait etre d'utiliser la fonctionnalité de split. Depuis le backlog, click droit sur…

Most likely your base url is wrong. I tested it and works on my side. Did you include the path if any ? like url/jira/rest....

This script works import requestsimport json # Replace these variables with your JIRA instance detailsgroupName = ''jira_url = ''api_endpoint = f'/rest/api/2/group/user?groupname={groupName}'url = jira_url + api_endpoint # Your JIRA credentialsapi_token = '' # Headers for the requestheaders = { 'Content-Type':…

I would remove this condition. For me issue.issueLinks.type is not returning what you are expecting but it's not really useful as it will branch over 0 issues if any. Regards

Did you follow this ? Using Personal Access Tokens | Atlassian Support | Atlassian Documentation You are using Token but also referencing HTTPBasicAuth

Hi @Sam 401 means permission error. You do not provide the right credentials. You should provide the credential as "basic {base64 encoded user:password}" Regards

It's how the tool is build in and also how much of project management methodology works. JIRA's hierarchy is designed to ensure each task has a clear and singular path of progression. A task having only one parent (such as a story or an epic) helps maintain a straightforward and understandable project structure. Allowing…

Did you try to compare issue.issuelink.type with Cloners ?

Hi @Bruno Jimenez Welcome to the community 1- project = PROJ and status = pending 2- Owner is empty and status in (Open, New) and updated < startOfMonth() Regards

Hi @Simay Paksoy Is your automation scope on both project ? Which condition is not met, the 1st or 2nd one ? It may be related to the 1st one where you should not use 'is cloned by' but Cloners Regards

Hi @Jira Admin Most o the time the user has rules in their inbox that delete/move emails from JIRA. Make sure it's not the case. Also sometimes it goes to spam. If you only have a user in this case it's most likely related to his configuration. Regards

Hi @[deleted] Have you try to not use a branch and access the field value directly? issue.epic.assignee.emailAddress Regards

Hi, @michelle_anderson Correct. Any issue can have only 1 parent using Parent Link. Regards