youngmon/atlassian-qna huggingface dataset:
Jira Automation - Child issues inherit Epic Link from Parent
Asked by Lea Casper:

Hello!

Like the title states, I am trying to set up a Jira Automation to have child issues inherit its parents' epic link.

On my team, we have an additional issue type called "New Feature", which is the parent to a group of stories. An Epic is a parent to a group of New Features. Epic -\> Features -\> Stories.

**The scenario:**

I want to move a feature, and therefore, a group of stories, to under a new Epic (the team found that it fit better under a different bucket). So I changed the parent link of the feature to the new Epic, and I changed the epic link of the Feature, but the 55 stories that we have under the feature all still have the old epic link. Do I need to go one by one changing these epic links? Or is there a way to automate that when a parent epic link changes, so does all of its children?

Thanks,

Lea


Answers:
author: Mark Segall
body: Hi [@Lea Casper](/t5/user/viewprofilepage/user-id/4564720) - To make sure I understand this correctly, You have renamed the native "Epic" issue type to "Feature" and created a custom issue type called "Epic". Then you updated the issue type hierarchy so that Epic resides above Feature. If this is correct, you do not need to do anything with the child stories. If you change the parent link of the Feature, all of the children will dynamically follow it to the new Epic and this would be reflected on any Advanced Roadmap Plans

comments: author: Lea Casper
body: Hi [@Mark Segall](/t5/user/viewprofilepage/user-id/4666637)

Actually, I created a new issuetype called New Feature, I think it's more similar to a Story. The epic remained the same! Epic resides above Feature and Story.


author: Mark Segall
body: Ok - In that case, you'll need some type of business logic that automation can leverage to identify the relationship between the New Feature and corresponding stories. For example, let's say that all of the stories have been linked to the new feature as blockers. In this case, your automation rule would look something like this:

* TRIGGER: Field Value Changed (Parent Link)  
  NOTE - Epic Link is not supported as a trigger, but Parent Link has proven to work instead.
* CONDITION: Issue Type = New Feature
* BRANCH (Linked Issues - Is Blocked By)
  * Edit Issue (Epic Link)
    * Copy from Trigger Issue


author: Bill Sheboy
body: Hi [@Lea Casper](/t5/user/viewprofilepage/user-id/4564720)

Just following up to check if this answered your question. If so, please consider marking this one as "answered". That will help others with a similar need find solutions faster. If not, please let the community know what help you need with the rule changes. Thanks!

Kind regards,  
Bill


Tags: jira-software
JIRA Automation - Create tasks / subtasks when a story is created
Asked by Jhan Knebel:

I'm currently using the Issue created trigger, but I want to just create the tasks under issue type: story, not any other issue type. Does anyone know how to configure JIRA to only run the trigger on one issue type, not all?


Answers:
author: Arkadiusz Inglot
body: Hi.

There is no way to limit rule execution base on issue type.

You can run it everytime and limit it by "if block" statement.

**Issue fields condition:**

* Field: issue type
* Condition: Equals
* Value: Story
URLs within Automation emails
Asked by Beth Wilkinson:

I have created an automation that will send an email to specified users when documents have been attached to the subtask.

Everything is working as expected except that when you click on the URL within the email, it states that "You don't have access to this issue". This happens even with the administrators of the project.

Any suggestions on what might be happening or is this a bug?

![DocumentsAdded.png](https://community.atlassian.com/t5/image/serverpage/image-id/284036i7E4FAB4C6E9EC77E/image-size/large?v=v2&px=999 "DocumentsAdded.png")![Email.png](https://community.atlassian.com/t5/image/serverpage/image-id/284037i14A078DF944ED160/image-size/large?v=v2&px=999 "Email.png")![Error.png](https://community.atlassian.com/t5/image/serverpage/image-id/284038i6687CCBB55B9FB9B/image-size/large?v=v2&px=999 "Error.png")


Answers:
author: Giovanni Melai
body: Hi [@Beth Wilkinson](/t5/user/viewprofilepage/user-id/5301190) ,

I think you can try to substitute

```
{{url}}|{{key}} - {{summary}}
```

with

```
<a href="{{url}}">{{key}} - {{summary}}</a>
```

Even if I'm not able to reproduce the behavior it seems to me that the link is created in the wrong way.

I hope this helps

comments: author: Beth Wilkinson
body: Thank you sooo much! This worked perfectly!!!


author: Bill Sheboy
body: Hi [@Beth Wilkinson](/t5/user/viewprofilepage/user-id/5301190)

Just following up to check if this answered your question. If so, please consider marking this one as "answered". That will help others with a similar need find solutions faster. If not, please let the community know what help you need with the rule changes. Thanks!

Kind regards,  
Bill


author: Beth Wilkinson
body: It did, but I don't have the mark it as answered like I have seen before. I will try and figure out what happened.


author: Mikael Sandberg
body: Use {{issue.url.customer}}, that will give you the portal link that the customer can access. The {{url}} that you are using only works for users that have agent access to the project.
Check if custom field is empty before close
Asked by Alexander M?nchrath:

Hello dear community, I have a question and hope that I get the help here.  
We have created a custom field "Release Note Information". Now this field should be filled only for stories and bugs.  
Here the automation should intervene. If the field is not empty, a warning should appear and inform the user that the information must still be entered before the ticket can be closed.  
I have already set it to check if it is a story or a bug and if the field is empty or not. But after that I can't find the right value. I don't want to send mails or enter something automatically. I want it to give a warning and not close the ticket before the field is filled.  
Is that even possible with automation? If yes, how?  
Thanks  
Alex


Answers:
author: Marco Brundel
body: Hi [@Alexander M?nchrath](/t5/user/viewprofilepage/user-id/5226968) ,

Welcome to the Atlassian Community.  

In your usecase I advise to use a validator on a workflow transistion.

You can ad the validator "Field Required Validator" on the transition to the 'Closed' status.  
So the issue can only been set to 'Closed' if the field is filled.

Is this a option for your situation?

Regards,

Marco Brundel


author: Hana Ku?erov?
body: Hi [@Alexander M?nchrath](/t5/user/viewprofilepage/user-id/5226968) ,

in your case I would create screen with your custom field and add it to the transitions, where you expect it to be filled. You can also add validator to these transitions, if you want to force your users to fill it.

Automation rule won't help here.

comments: author: Bill Sheboy
body: Hi [@Alexander M?nchrath](/t5/user/viewprofilepage/user-id/5226968) -- Welcome to the Atlassian Community!

Adding to the answer from Hana...

Automation rules run (i.e., trigger) *after* something has happened. And for your scenario the rule could not trigger until after the issue has already transitioned. That would not help ensure the field is completed first.

Kind regards,  
Bill


author: Alexander M?nchrath
body: Thanks for the answers. I had not thought about the condition in the workflow.
Creating automation across 2 projects
Asked by Janette Kim _I_:

Is there a way to set up automation across 2 different projects?

Every time a ticket in project A hits a certain status, I want a new ticket to be made in project B.

The reason is because we don't want everyone in project B to have access to project A.


Answers:
author: Mikael Sandberg
body: Hi [@Janette Kim _I_](/t5/user/viewprofilepage/user-id/5326897),

Welcome to Atlassian Community!

Yes, that is possible and is fairly easy to set up. It would look something like this:

![Screenshot 2023-09-26 at 1.28.38?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/283091i99EEBC957194E111/image-size/large?v=v2&px=999 "Screenshot 2023-09-26 at 1.28.38?PM.png")This is a simplified example, but it should get you started.

comments: author: Janette Kim _I_
body: Awesome I'll test this out [@Mikael Sandberg](/t5/user/viewprofilepage/user-id/853579) !


Tags: jira

unknown-hosting-type
How do I send an automation email based on the day of the week?
Asked by Alex Waugh:

Hello,

I have a rudimentary IT Service Management project for a small helpdesk team. Currently I have an automation that when a ticket is submitted, it sends an email to the team members via email. From there, one of them assigns themselves the ticket.

Recently we have created a coverage schedule so I'm looking for the following to notify specific team members based on the day of the week:

**If a ticket is submitted on Monday, send an email to these specific email addresses.**

**If a ticket is submitted on Tuesday, send an email to these specific email addresses.**

And so on...

I think I need to compare two values but I'm not sure exactly what I need to compare to check for just the day of the week. There might also be an easier way to do this and I'm not aware of the feature. Thanks in advance.


Answers:
author: Mikael Sandberg
body: This is what I would do, I would create if/else conditions that convert the created date to fullDate using [{{\[date\].\[dateformat\]}}](https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#--) and then compare to see if it contains Monday, Tuesday and so forth in the if/else. And each if/else would then send the email to the specific emails. Something like this:

![Screenshot 2023-09-26 at 1.04.23?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/283087iEABEEB91736CE961/image-dimensions/237x329?v=v2 "Screenshot 2023-09-26 at 1.04.23?PM.png")

comments: author: Alex Waugh
body: Thanks so much Mikael. This was exactly what I was looking for. Appreciate it!


author: Bill Sheboy
body: Hi [@Alex Waugh](/t5/user/viewprofilepage/user-id/5070310)

Is the only thing different the recipient email addresses with the email body the same for all?

If so, you can make a simple and easy to maintain rule using the new [Lookup Table action](https://community.atlassian.com/t5/Automation-articles/New-Automation-action-Create-lookup-table/ba-p/2311333) automation rules. Perhaps like this:

* trigger: issue created
* action: re-fetch issue (I always add this after the issue created trigger to slow down the rule; that trigger can run so fast the issue data is not yet available for the rule.)
* action: create lookup table
  * name: tblCoverageScheduleEmails
  * row
    * key: Mon
    * value: person1email;person2email
  * row
    * key: Tue
    * value: person3email;person4email;person5email
  * ...
* action: send email, converting the current date into the day of the week using [date/time functions](https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/)
  * the to email address would be:
    * {{tblCoverageScheduleEmails.get(now.format("E")).split(";")}}
  * email body...

Kind regards,  
Bill
Compass GraphQL query via Automation
Asked by Ken Young:

There have been minimal posts about using GraphQL via the web request component so I am not sure if this is even possible.

I am trying to integrate some of our Jira activities with compass via automation, but there are challenges in doing so via graphql. The current implementation of web-request component doesnt' allow you sent the sent the same header twice in the request (Compass currently requires you sent 'X-ExperimentalApi' to access the api's (you need to currently send two). When I limit down to a single header, I get a 400-Bad Request response.

My questions are:

1. Is this a limitation, or is there a way to two "headers" into a single header in the automation component
2. Are there any examples that can be shared of successful graphql queries being used.

Thank you


Answers:
author: Bill Sheboy
body: Hi [@Ken Young](/t5/user/viewprofilepage/user-id/4596309)

The only thing I found related to this was this automation suggestion:

Support additional auth types for incoming and outgoing webhook components, e.g. to support GraphQL Actions, or NTLM auth <https://jira.atlassian.com/browse/AUTO-182>

You may want to also post this question in the developer community to see if you get more information: <https://community.developer.atlassian.com/>

Kind regards,  
Bill
Integrate Jira Service Management With iLert system.
Asked by Jessica:

Hi Team!

Currently I would like to Integrate Jira Service Management With iLert system with below 2 fucntions.

1. When Jira created --\> create a iLert alert automatically

2. Whem Jira status being updated to "ToDo","In Progress" --\> Update the alert status from "Pending" to "Accepted"

3. When Jira updated to "Done" --\> Update the alert status to "Resolved"

Looking forward for your professional insights\~ :)


Answers:
author: Peter_DevSamurai
body: Integration between Jira Service Management and iLert, or any other alerting and incident management system, typically involves utilizing webhooks, APIs, or intermediary integration platforms. Your goals involve synchronizing the status between Jira issues and iLert alerts, which is a common requirement for maintaining coherent operational workflows across platforms.  

Suggestions for Integration:  
**1. Use of APIs/Webhooks:**   
- Both Jira and iLert provide APIs and webhooks.  

**2. Using Jira webhooks,**   
- you can trigger HTTP callbacks to iLert when an issue is created or its status is changed in Jira, allowing you to automate the creation and updating of alerts in iLert.  

**3. Use of Integration Platforms:**   
- Platforms like Zapier or Integromat can facilitate integration by providing pre-built connectors and logic to sync data between Jira and iLert without requiring coding knowledge.  

**4. Create Automation Rules in Jira:**   
- Automation rules in Jira can be configured to invoke webhooks or perform actions when issues meet certain conditions, such as a status change to "ToDo", "In Progress", or "Done".
Confluence automation - error on CQL query
Asked by M?lanie Liguet:

Hi,

I try to use Confluence automation on cloud

I need to archive all pages that are not updated since 4 months.

I did many CQL query, but i have always an error message on CQL.

automation and CQL query are very simple

![automation-rule.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/282737iC4745FF26EF84F0A/image-size/large?v=v2&px=999 "automation-rule.PNG")![auditLog.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/282739i81FAD6C5B77AD69F/image-size/large?v=v2&px=999 "auditLog.PNG")

What is wrong on this CQL query ? (if I increase the number of months I still get the same message)

Regards


Answers:
author: Mike Monk
body: Can you try adding a "For Each Entity" branch and then move the CQL into that Branch

comments: author: Bill Sheboy
body: Hi [@M?lanie Liguet](/t5/user/viewprofilepage/user-id/4533707)

Adding to Mike's answer, please look here to learn more about using branches in a rule like yours:

<https://support.atlassian.com/cloud-automation/docs/branches-in-confluence-automation/#For-each-CQL-result--related-entities->

Kind regards,  
Bill
Is there anyway to get a consolidated log of all the automation in an instance?
Asked by Catalina Pabon:

We need to be able to see what are the automations being used the most and identify the number of executions without having to go one by one.

Is there any way?

Many thanks,

Catalina


Answers:
author: Bill Sheboy
body: Hi [@Catalina Pabon](/t5/user/viewprofilepage/user-id/3613781)

Rule execution counts is one of the automation limits that impacts an instance. (Although that measure is getting a lot of community attention in the post that Jack linked to...)

You may find more by viewing the **Performance Insights** from the global rule configuration. This can help find rules that run long, run often, fail frequently, get throttled, etc. Please look here to learn more about that report, and watch for updates as the service limits are changing:

<https://support.atlassian.com/cloud-automation/docs/view-performance-insights-for-automation-rules/>

Kind regards,  
Bill


author: Jack Brickey
body: Hi [@Catalina Pabon](/t5/user/viewprofilepage/user-id/3613781) , are you referring to global/multi-project or single project. The former can be found under admin \> system \> global automation \> usage tab. However, single project rules will not be shown there at this time. With the proposed rollout of changing single project rules from unlimited to limited I believe this will change according to this article from Kevin Bui - [Introducing-our-new-packaging-model-for-Jira-Cloud-Automation](https://community.atlassian.com/t5/Automation-articles/Introducing-our-new-packaging-model-for-Jira-Cloud-Automation/ba-p/2446099) "*From October 1st -31st, 2023, you'll see a Preview option on the Global Automation screen next to the current Usage tab."*


author: Tim C
body: Yeah, via "Global automation" ... under "system" (main admin) ...

\<yourinstance\>.atlassian.net/jira/settings/automation#/tab/usage
Jira Automation sending POST request to python script
Asked by Sureshkumar S:

When I send a post request to python using Jira automation "SEND Web Request: POST" I got the below error.  

Server: squid  
Mime-Version: 1.0  
Date: Fri, 22 Sep 2023 20:06:16 GMT  
Content-Type: text/html;charset=utf-8  
Content-Length: 3114  
X-Squid-Error: ERR_ACCESS_DENIED 0  
Vary: Accept-Language  
Content-Language: en  
X-Cache: MISS from ip-10-125-126-94.net.atlassian.com  
Via: 1.1 ip-10-125-126-94.net.atlassian.com (squid)  
Connection: keep-alive


Answers:
author: Marcus Jones
body: The solution is to add the port 5000 in /etc/squid/squid.conf :

acl SSL_ports port 443 563 5000

However, adding to the SSL_Port section is OK, but it means everyone gets access to it.

You can restrict even further, so that only a single IP address, or multiple IP addresses can only access this port! Just in case you don't want the whole network to have access.

comments: author: Sureshkumar S
body: Sorry, Marcus. This is my 1st time developing an API program. Please elaborate on how we need to configure /etc/squid/squid.conf. My code is my local machine (Windows), and I exposed my local host online using the Flask library. I want to send the post request to my local dev env.
Remove account from crowd-administrators
Asked by Marian:

hi, We are trying to migrate from Bitbucket on-prem server to Cloud, but the Migration tool does find this an issue "duplicate email" and we can't move forward. The user is set in "crowd-administrators", and I can't add others or remove that one.

PS: the format of the account is "username_crowd"

thank you.


Answers:
author: Marian
body: got these from a ticket:

<https://confluence.atlassian.com/crowdkb/restoring-passwords-to-recover-admin-user-rights-via-database-283642653.html>

<https://confluence.atlassian.com/crowdkb/restore-passwords-to-recover-admin-user-rights-using-system-properties-998644535.html>

<br />

<https://confluence.atlassian.com/crowd/deleting-or-deactivating-a-user-33423499.html>


Tags: bitbucket-data-center

data-center
Cannot access Bitbucket workspace
Asked by davefx:

I just created a new workspace, and when trying to access it, I'm getting an error screen.

The workspace is listed in the list of workspaces, but when clicking on it I get the following message:

Resource not found {#toc-hId--353433967}
----------------------------------------

Return to the previous page or go back to your [dashboard](https://bitbucket.org/).


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

Welcome to the community!

Could you please ensure your groups have product or admin access to the newly created workspace in Atlassian Admin? If not, add the group to the product to grant access, then try to access the workspace again.

Let me know how it goes.

Regards,  
Syahrul


Tags: bitbucket-cloud

cloud
Cant create new workspace
Asked by osiztechnologies:

Hello ,

We are facing issue that their is no create workspace option.Whats the reason for that and i need to know how to fix this issue .  

Here i have shared the image of my bitbucket account and can see that their no option of create workspace and we dont see the option the account .


Answers:
author: Theodora Boudale
body: Hi [@osiztechnologies](/t5/user/viewprofilepage/user-id/1788323),

Bitbucket workspaces can now be created only in Atlassian Administration (<https://admin.atlassian.com/>).

You can check the following documentation for the steps you need to follow to create a new workspace:

* <https://support.atlassian.com/bitbucket-cloud/docs/create-your-workspace/>

Please feel free to reach out if you have any questions.

Kind regards,  
Theodora

comments: author: osiztechnologies
body: Hello Team,

Thanks for your assistance


author: Theodora Boudale
body: You are very welcome. Please feel free to reach out if you ever need anything else!


author: osiztechnologies
body: ![Screenshot from 2024-07-02 14-39-37.png](https://community.atlassian.com/t5/image/serverpage/image-id/332968i60012290E6500065/image-dimensions/6x1?v=v2 "Screenshot from 2024-07-02 14-39-37.png")

comments: author: osiztechnologies
body: d


Tags: bitbucket-cloud

cloud
email notifications
Asked by ??????? ?????:

Hello,

I stopped receiving email notifications at least when it comes to comments and updates on pull requests.

Other team members are receiving notifications.

Thanks in advance.


Answers:
author: Nikola Perisic
body: Hi [@??????? ?????](/t5/user/viewprofilepage/user-id/5533644)

This is because your email address has been added to the Atlassian suppression list. Raise a support ticket for them and asked for your email to be checked if it's on the suppression list. Usually it is.

comments: author: ??????? ?????
body: Thanks a lot! I'll try


Tags: bitbucket-cloud

cloud
Terraform pipeline and state lock problem
Asked by mc84:

I created a bitbucket pipeline, that looks like this. A first step will simply do:  

```
 - /bin/sh scripts/createDeployConfigFile.sh
 - terraform init -backend-config=./deploy.conf
 - terraform validate
 - terraform plan -out=tfplan
```

The second step is triggered manually and (should) simply do:  

```
- terraform apply tfplan
```

<br />

Have in mind that the first step exports the following artifacts:  

```
artifacts:
 - tfplan
 - terraform.tfstate
 - .terraform/**
 - .terraform.lock.hcl
```

and that the above commnads correctly edploy the environment when executed in my workstation (with the same backend).  
Any one had a similar issue? As a workaround I issued terraform init -backend-config=./deploy.conf even in the second step, and this resolved the problem, but I'm feeling uncomfortable because some of the steps and artiffacts are executed two times.


Answers:
author: Theodora Boudale
body: Hi [@mc84](/t5/user/viewprofilepage/user-id/5533904) and welcome to the community!

If you run this Pipelines build on Atlassian's infrastructure, every step of the build runs on a different Docker container. For every step of the build, a Docker container starts. The repo is cloned in that container (unless you have disabled cloning), and then the commands of that step's script are executed. When the step finishes, the Docker container gets destroyed.

I'm not familiar with terraform, but is it possible that the commands in the first step are doing some additional tasks other than generating the files you have defined as artifacts?

When you run these commands on your workstation, I'm assuming that you execute them in the same environment. A second step in a Pipelines build runs in a separate Docker container, so in a different enviornment than the first step. I suggest looking into the exact tasks performed by the command you need to rerun in the second step, and maybe reach out to terraform's community or support team.

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud

terraform