youngmon/atlassian-qna huggingface dataset:
Automation plugin: stuck at creating subtasks in a rule
Asked by Pepijn:

Hi there,

I am keep getting stuck when I try to create sub-tasks once a component it's value is changed.

See the screenshot: the loading icon keeps in a loop and nothing happends.

![automation-stuck-on-creating-subtasks.png](https://community.atlassian.com/t5/image/serverpage/image-id/205577i6A1352F9B03FB738/image-size/large?v=v2&px=999 "automation-stuck-on-creating-subtasks.png")

I tried already several browsers, but no luck.

Any help please?


Answers:
author: Patrick
body: Dear all,

same problem here and it is now November 2022. I have tried using different browsers like Chrome, etc. and every time I get the same loading icon.

Clearing the cache doesn't help me here either.

I will also create a ticket with Atlassian and hope for a quick solution!

Br

Patrick


author: Dan Tombs
body: Hi [@Pepijn](/t5/user/viewprofilepage/user-id/4984874)

This seems like a big over anything wrong with your rule itself. My advice would be to raise this with Atlassian directly to see if it has already been reported. My only other bit of advice would be to do the basic support troubleshooting of clearing browser cache etc.

Kind Regards,

Dan Tombs

comments: author: Pepijn
body: Hi Dan,

Thank you for your reply.

I think this is a bug since all the other actions do work.

Only this one is stuck with the loading icon.

I don't think it's browser cache related, but I will try just to be 100%.

I will get back to you.

Regards, Pepijn


author: Pepijn
body: Hi Dan,

I tried clearing the cache, but it didn't help.

Also I tried to see this on a different computer with the same result.

It really seems like a bug in an endless loop.

How can I contact Atlassian directly?

Thanks for your time.

Kind regards, Pepijn


author: Dan Tombs
body: Hi [@Pepijn](/t5/user/viewprofilepage/user-id/4984874)

If you go to support.atlassian.com and then at the bottom click contact support. Then just fill in the form and you should be good.

Dan


author: Pepijn
body: Hi [@Dan Tombs](/t5/user/viewprofilepage/user-id/4172448) ,

Thanks for your reply again.

I tried to fill in the form, but I cannot submit the form when selecting the plug-in.

See also my screenshot:

![cannot-submit-form.png](https://community.atlassian.com/t5/image/serverpage/image-id/205774iE412DBD597BF09B0/image-size/large?v=v2&px=999 "cannot-submit-form.png")

It seems not triggering to show any submit button.

With other plug-ins I don't have any problem.

Is that plug-in maybe bugged?

Looking forward to hear from you again.

Kind regards, Pepijn


author: Jana Frank
body: Hello Pepijn,

I experience the same problem with a very simple automation rule with just a manual trigger, so I do not think one of the rule components is the problem.

Also I cannot open a support request as our Jira is not cloud version and thus not running on a URL like **mysitename.atlassian.net**


author: Odrzyw?? ?ukasz
body: Hello guys.  
We have this same problem on Jira server/DC v8.20.6.  
A workaround is to create not a subtask, but to create a issue and set the issue type as a subtask.
Logical names for webhooks
Asked by Martin Cleaver:

When I create a webhook in e.g. Jira Automation, I get given a random URL for the endpoint. I'd like to be able to customize it. Instead of ab45345dfe, let me use myapp/myresource/myendpoint.

Random slugs are difficult to understand and impossible to remember.

Architecturally they offer only a physical address and make it harder to build layered services.

Perhaps this ability is a target of Forge?


Answers:
author: frother
body: Hi Martin,

Unfortunately this isn't something that is going to be changed any time soon, as this path needs to be unique across every instance using automation, not just your instance. So if we had another instance with the same path then we would have conflict; which is why we generate a slug to ensure its uniqueness.

Sorry,  
Scott.


Tags: cloud

webhook
Automation f?r "neue Issues"
Asked by Harald:

Hallo zusammen,

wir haben eine Automation in unserem Jira-Projekt erstellt.

Wir wollen, wenn wir zu einem Epic einen untergeordneten Issue erstellen eine Automation zuweisen, dass alle Labels aus dem Epic dem neuen Issue zugeordnet werden.

Dies gilt in allen Kombinationen, wenn der Issue direkt als untergeordnet erstellt wird.

Egal, ob Story, Task oder aus einem Task ein Sub-Taks.

Irgendwie funktioniert aber der Trigger

"Vorgang erstellt"

nicht so, wie wir uns das gedacht haben. Es wird kein Label kopiert.

Was machen wir falsch?

Gru?

Harald


Answers:
author: Stefan Salzl
body: Hi Harald,

K?nntest du uns bitte einen Screenshot von deiner derzeitigen Automation Rule bereitstellen? Das hilft der Community zur besseren Analyse ;)

So weit ich deine Anforderung richtig verstehe ist der Einstiegspunkt ja nicht die Aktion "create issue" sondern wann immer ein issue an ein epic geh?ngt/gelinkt wird.

Der folgende Artikel beschreibt ein sehr ?hnliches Problem und sollte f?r die L?sung sehr hilfreich sein:  
<https://community.atlassian.com/t5/Jira-Software-questions/Automation-on-Epic-Link/qaq-p/1713453>

Des weiteren glaube ich zu wissen, dass Issues auf Sub-Tasks-Ebene nicht zu einem Epic gelinkt werden k?nnen (via Epic-Link).

Bitte lass uns wissen ob diese Antwort hilfreich war.

LG  
Stefan
View work log at JIRA - Feature Level
Asked by Shashikant Mahadik:

Hi ,

We have additional levels of hierarchy in our JIRA , project-\>feature-\>epic-\>story-\>sub task. We logged hours for stories and sub tasks

Is it possible to show / Display the sum of logged hours on Feature level ?


Answers:
author: Ravi Sagar _Sparxsys_
body: Hi [@Shashikant Mahadik](/t5/user/viewprofilepage/user-id/4984018)

Not out of the box, you can either build automation to roll up numbers to above level. It may not be straight forward but possible.

I normally rely on eazyBI to build a report to show progress at higher levels. If you are already using Advanced Roadmaps then eazyBI can use that hierarchy to show you this roll up number at any level.

Ravi

comments: author: Shashikant Mahadik
body: Thank you [@Ravi Sagar _Sparxsys_](/t5/user/viewprofilepage/user-id/853596)

I will try eazyBI. :-)


author: Rahul_RVS_Support
body: Hi [@Shashikant Mahadik](/t5/user/viewprofilepage/user-id/4984018)

Welcome to the community !!

If you are fine with a mktplace app, you can have a look at our add-on to get this data -

[Issue Hierarchy Reports](https://marketplace.atlassian.com/apps/1228019/issue-hierarchy-reports?hosting=cloud&tab=overview)

and generate insights such as:

- View the full Jira Issue Type hierarchy of Linked issues,  
Portfolio/Advanced Roadmaps, Epics, and Subtasks up to 10 levels.

- % complete based on time spent and story points at each hierarchy level

- Sum up Time Spent, Org Estimate, Time Rmng, custom number  
fields

![Links HIerarchy.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/207225i09D42F892B18C5BC/image-size/large?v=v2&px=999 "Links HIerarchy.PNG")
Unable to update custom field when issue is transitioned to 'Closed' status
Asked by Aman Kumar Jain:

##### We have created a custom field (Resolution Date) and looking to update the field when ticket is transitioned to closeD. {#toc-hId--1646886882}

![Screenshot 2022-07-10 at 2.16.38 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/205328i065B0336A3C16ABB/image-size/large?v=v2&px=999 "Screenshot 2022-07-10 at 2.16.38 PM.png")  
I get the following errors:  
Unknown fields set during edit, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored - Resolution Date (customfield_XXXXX)  
No fields or field values to edit for issues (could be due to some field values not existing in a given project): ABC-XXXX  
NOTE:  
I have also created an automation to clear the field when issues move to any other status - that works perfectly fine.


Answers:
author: Nic Brough -Adaptavist-
body: Welcome to the Atlassian Community!

Ok there's a couple of things here.

First, why have you added a field called "resolution date"? Jira already has that, and it calculates it automatically, you don't need automations for it to work.

Second, the problem in the automation is what it says it is - the automation can't find your custom field, it's not associated with the project. This might actually be caused by the first question - the automation is looking for your custom field, but finding the system field first and getting confused.

I'd recommend getting rid of your custom resolution date field and not bothering with this automation, as you don't need it.

comments: author: Timothy Ryner
body: [@Nic Brough -Adaptavist-](/t5/user/viewprofilepage/user-id/781454) , there is a bug where the Resolved Date is not being set if Automation is used to set the Resolution. Might be how [@Aman Kumar Jain](/t5/user/viewprofilepage/user-id/4983539) arrived at this point?

[\[JIRAAUTOSERVER-60\] Setting resolution field as an edit issue action does not set the resolved date of issue - Create and track feature requests for Atlassian products.](https://jira.atlassian.com/browse/JIRAAUTOSERVER-60)


author: Nic Brough -Adaptavist-
body: Possible, if they're on an old Server version of Jira
Alternating assignee from week to week
Asked by Kumar:

Hi,

How would you go about setting the assignee for a Jira service ticket like this:

person1 for week1

person2 for week2

person1 for week3

and so on throughout the year.

Thanks,

Kumar


Answers:
author: Bill Sheboy
body: Hi [@Kumar](/t5/user/viewprofilepage/user-id/3094590)

Time-based assignment rotation is not one of the built-in options: <https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Assign-issue>

You could probably build this by performing math on the current week number with some if/else conditions, however...

What have you considered for the impacts of this approach? For example, time-based-only would disregard the current workload of people, and so create some potential challenges.

Kind regards,  
Bill
Assigning Value to 'Parent' When Creating A Task By Automation
Asked by Shrinidhi Selvakumar:

Hello,

When creating a Task using Jira automation, is it possible to set the trigger event (in this case a Story) as the Parent of the newly created Task?

BR

Shrinidhi


Answers:
author: Bill Sheboy
body: Hi [@Shrinidhi Selvakumar](/t5/user/viewprofilepage/user-id/4831071) -- Welcome to the Atlassian Community!

If I understand your question correctly, the answer is: yes, it is possible to set a parent's field when a child issue is created. Please try using a Branch to the Parent in order to access its fields.

Kind regards,  
Bill

comments: author: Shrinidhi Selvakumar
body: Can you please share me the steps..


author: Bill Sheboy
body: Writing automation rules is a lot about experimentation and learning (e.g. reading documentation and reading posts), and I respectfully suggestion trying both. To help you get started, here are some draft steps I suggested earlier:

* trigger: issue created
* action: re-fetch (This helps prevent timing errors after the issue created trigger)
* condition: issue type is Task
* branch: to the parent
  * action: edit the issue, copy data as needed from the Trigger Issue
Jira Automation does not work for Service Project
Asked by Nick de Pal?zieux:

I have a global Jira automation rule that sets an issue's due date based on the start date of the release specified in the "Fix Versions" field.

This automation works fine for all of our "Software Projects". However, it does not appear to work for our "Service Project".

When setting the "Fix Versions" field of a Service Project issue, I can see that the automation triggers by looking at its audit log. The audit log claims "Field values changed MYPROJ-123". But when I reload that issue, the "Due Date" field is still not set.

Is this functionality not available for Service Management Projects?


Answers:
author: Jack Brickey
body: Could you share your rule here? I have not used fix versions in my JSM projects but willing to test it out and see what I experience.

comments: author: Nick de Pal?zieux
body: Thanks for your response [@Jack Brickey](/t5/user/viewprofilepage/user-id/853369) here is the rule:  

```
{

"cloud": true,

"rules": [

 {

"id": 6817145,

"name": "Set due date when setting fix version",

"state": "ENABLED",

"description": null,

"created": 1656572539782,

"updated": 1656678400201,

"trigger": {

"id": "129907158",

"component": "TRIGGER",

"parentId": null,

"conditionParentId": null,

"schemaVersion": 2,

"type": "jira.issue.field.changed",

"value": {

"changeType": "VALUE_ADDED",

"fields": [

 {

"value": "fixVersions",

"type": "field"

 }

 ],

"actions": []

 },

"children": [],

"conditions": [],

"connectionId": null

 },

"components": [

 {

"id": "129907159",

"component": "ACTION",

"parentId": null,

"conditionParentId": null,

"schemaVersion": 10,

"type": "jira.issue.edit",

"value": {

"operations": [

 {

"field": {

"type": "ID",

"value": "duedate"

 },

"fieldType": "duedate",

"type": "SET",

"value": "{{issue.fixVersions.startDate.minusBusinessDays(3)}}"

 }

 ],

"advancedFields": null,

"sendNotifications": true

 },

"children": [],

"conditions": [],

"connectionId": null

 }

 ],

"canOtherRuleTrigger": true,

"notifyOnError": "FIRSTERROR",

"projects": [],

"labels": [],

"tags": [],

"ruleScope": {

"resources": [

"ari:cloud:jira::site/0093e998-e2ec-4419-9b2d-c2df9137d717"

 ]

 },

"writeAccessType": "UNRESTRICTED",

"collaborators": []

 }

 ]

}
```


author: Nick de Pal?zieux
body: Just now I see that for an issue in a Software Project - where I thought the automation was working fine - the audit log shows that the automation ran, but the allegedly modified issue does not have the due date set.


Tags: jira-service-management-cloud
Trouble using data from a custom field in Jira Automation
Asked by Dave F:

I have a custom drop down called "delivery date flexibility" with values such as "\<6 months (5)" or "\<1 month (20)".  

Using a Log Action in Jira Automation to try to find the right syntax to use I'm not seeing values as expected.

The line in my Log Action is as follows:

```
{{delivery date flexibility}} . {{delivery date flexibility.id}} \ {{issue.customfield_10259}} \ {{issue.customfield_10259.name}} \ {{issue.customfield_10259.displayName}} \ {{issue.delivery date flexibility}} . {{delivery date flexibility.displayName}} . {{delivery date flexibility.name}} . {{delivery date flexibility.length()}} . {{delivery date flexibility.replaceAll("(\D)","")}} . {{delivery date flexibility.match("(\d)")}}
```

This returns:

\<2 months (13) . 10259 \\ \\ \\ \\ \<2 months (13) . . . . .

So, these work as expected, so I've got the field name right:

{{delivery date flexibility}} returns the expected value "\<2 months (13)"

{{issue.delivery date flexibility}} returns the expected value "\<2 months (13)"

{{delivery date flexibility.id}} returns the expected field ID "10259"

These don't work and I expected that they would. Where am I going wrong with these? Ultimately I want to just extract the digits in the braces from the string, e.g. "13" to use in a formula.

{{issue.customfield_10259}} returns null. I expected "\<2 months (13)". Adding .name or .displayName also returned null

{{delivery date flexibility.length()}} returns null. I expected "14"

{{delivery date flexibility.replaceAll("(\\D)","")}} returns null. I expected "213"

{{delivery date flexibility.match("(\\d)")}} returns null. I expected "213"


Answers:
author: Dave F
body: Fooling around trying to find Using .value is mentioned in the customfield smart value doco, but only in passing.

It would have been nice if it were given it's own section heading as it's critical for getting the value out. That said:

* {{issue.customfield_10259.value}} still returned null
* {{delivery date flexibility.value.length()}} returned 14
* {{delivery date flexibility.value.replaceAll("(\\D)","")}} returned 213

At the risk of giving myself an internet point. I'm answering my own question as I thought this info might also help someone else one day.


Tags: custom-field

jira-cloud

smart-value
Hola como que rol de jira puedo usar para cargar tickets masivos que no sea trusted?
Asked by Cindy Delgado:

Hola quisiera saber si puedo utilizar otro rol que no sea trusted y que no tenga muchos permisos para cargar tickets masivos?

Gracias


Answers:
author: Ignacio Pulgar
body: Hola [@Cindy Delgado](/t5/user/viewprofilepage/user-id/4977428) ,

Entiendo que necesitas dar el permiso *Bulk Change.*

Si es as?, puedes configurar qu? grupos tienen el permiso *Make Bulk Changes* aqu?:

https://*TU_SITIO*.atlassian.net/secure/admin/GlobalPermissions!default.jspa

Cambia *TU_SITIO*para poner la direcci?n que aplique en tu caso.

Si quieres que todos los usuarios puedan hacer cambios masivos, puedes seleccionar el grupo *jira-software-users*.

Si quieres limitar este permiso, lo cual puede ser buena idea, puedes crear un nuevo grupo llamado *bulk-change*, a?adir los usuarios a los que desees dar ese permiso a dicho grupo, y configurar el grupo en la URL que puse m?s arriba, para que reciba ese permiso.

Espero te sea de ayuda.

Un saludo

comments: author: Cindy Delgado
body: Hola gracias por tu respuesta, la opci?n que necesito es crear varios tickets masivamente , tengo entendido que los admin y los que tienen rol de trusted pueden hacerlo sin embargo el rol trusted tiene muchos permisos que quisiera que no tuvieran estos usuarios, no hay un rol para solo crear tickets masivos?


author: Ignacio Pulgar
body: Hola [@Cindy Delgado](/t5/user/viewprofilepage/user-id/4977428) ,

El permiso global Make Bulk Changes que mencion? en mi anterior comentario creo que es lo que necesitar?as.

Pru?balo y si encuentras alg?n problema, com?ntalo por aqu? y lo vemos.

Un saludo


Tags: cloud
How to migrate source code to GIThub
Asked by B Vemireddy:

I am new to Github and trying to migrate source code from Bitbucket to GitHub . I am able to successfully login to GIthub and crated a repository. However when i am trying to import (cloned URL from Bitbucket is not working). Throwing error -No source repositories were detected at [https://bitbucket.\*\*\*\*.git](https://bitbucket.****.git). Please check the URL and try again. Please advice .


Answers:
author: Ben
body: Hi [@B Vemireddy](/t5/user/viewprofilepage/user-id/5469617)

Jumping in as I've not seen a response from anyone in our community.

The standard URL format for a Bitbucket Cloud repository is as follows:

* <https://bitbucket.org/workspaceID/reposlug.git>

We no longer allow basic username/password authentication over HTTPS so this might be why you are unable to gain access to it on GitHub, in which case you'll need to create an [App Password](https://support.atlassian.com/bitbucket-cloud/docs/create-an-app-password/) or a [Repository Access Token](https://support.atlassian.com/bitbucket-cloud/docs/repository-access-tokens/) first with **Read** permissions and then include this in the URL:

* **APP PASSWORD FORMAT:** <https://USERNAME:APP_PASSWORD@bitbucket.org/workspaceID/reposlug.git>
* **ACCESS TOKEN FORMAT:**   
  <https://x-token-auth:APP_TOKEN@bitbucket.org/workspaceID/reposlug.git>

If this still fails, I'd suggest reaching out to the Github community.

Hope this helps.

Cheers!

- Ben (Bitbucket Cloud Support)


Tags: bitbucket-cloud

cloud
I logged into my bitbucket account and No repos are found
Asked by mtaufiq81:

Today I logged into my bitbucket account and all my repositories are gone. The workspaces are available but all the repos are gone.


Answers:
author: Syahrul
body: G'day, [@mtaufiq81](/t5/user/viewprofilepage/user-id/5469616)

I see that your account still has access to multiple workspaces and repositories. Could you please navigate to the following URL and open the workspace \> repositories to view the repositories you have access to?

<https://bitbucket.org/account/workspaces/>

Let me know how it goes.

Regards,  
Syahrul


Tags: bitbucket-cloud

cloud
X-Hub-Signature and Signature generated with payload and secret does not match
Asked by Manoj Khiyani:

On repo push event, I'm generating the SHA256 value and comparing it with the request header but the keys do not match.


Answers:
author: Patrik S
body: Hello [@Manoj Khiyani](/t5/user/viewprofilepage/user-id/5469511) and welcome to the Community,

When enabling the webhook security feature, Bitbucket Cloud will generate an HMAC signature and provide it in the request header named X-Hub-Signature. This signature is generated. The signature is calculated based on the payload contents, your secret token, and a hashing algorithm (sha256).

It might be the case that your implementation of the validation is not hashing the exact same content as Bitbucket Cloud, thus representing a mismatch.

I would suggest following the instructions of the following article to understand the exact content that is hashed, and also some example code snipper (Java and Python) on how the validation can be done :

* [Validating webhook deliveries](https://support.atlassian.com/bitbucket-cloud/docs/manage-webhooks/#Validating-webhook-deliveries)

Hope that helps! If you have any questions, feel free to ask.

Thank you, [@Manoj Khiyani](/t5/user/viewprofilepage/user-id/5469511) !

Patrik S


Tags: bitbucket-cloud

cloud
Response code 429 (Too Many Requests) with Renovate scans
Asked by chris_flynn:

We use a [Self-hosted Renovate](https://docs.renovatebot.com/self-hosted-configuration/) to scan our Bitbucket Cloud repositories for dependency updates. It had been working fine for a while, but lately we have been getting constant "429 - too many requests" errors. These have made the scans completely useless. How can I figure out why this problem has started to occur suddenly?


Answers:
author: Syahrul
body: G'day, [@chris_flynn](/t5/user/viewprofilepage/user-id/3606357)

The error 429 (Too Many Requests) occurs because your account exceeds the rate limits. My observation suggests that your scan makes over 1,000 API requests per hour, exceeding the limit. You can refer to our Rate-limit page to understand how we calculate the rate-limit.

[Bitbucket API request limits](https://support.atlassian.com/bitbucket-cloud/docs/api-request-limits/)

If you need more detailed information, please create a support ticket with us on our [Support portal](https://support.atlassian.com/contact).

Regards,  
Syahrul

comments: author: chris_flynn
body: Hi [@Syahrul](/t5/user/viewprofilepage/user-id/744536)

Thank you very much for your response and help. I will open a ticket to find out more details about our requests, because I don't see how it is possible that we are hitting that limit. As soon as I start the Renovate scan I get the error message and there shouldn't be anything else making requests to the Bitbucket API on our account.


Tags: bitbucket-cloud

cloud