When will Jira automation be supported for Compass components?

[Joosep Ilves]

Hey,

According to

https://support.atlassian.com/jira-software-cloud/docs/what-are-compass-components/

Jira automation is not yet supported for Compass components

When do you expect the support for Jira automation to be finished?

Best,

J.

[Katie Silver · Accepted solution]

Hi @Joosep Ilves - it's in development now. I'm hoping it will be completed by the end of April, but it could go a little longer. I'll post here when it's out! 

Thanks,

Katie - Compass PM

[Vladyslav Bakuta]

@Katie Silver, thank you for the update!

The Compass indeed looks like a powerful tool that will significantly assist my team. However, we actively use automation, especially for task creation. It's critical for us to have the capability to define the component during task creation through automation.

Could you please let me know if you have any updates on the implementation timeline? 

[Katie Silver]

Hi @Vladyslav Bakuta , it looks like the work was delayed a little bit, so right now we are targeting end of May. However it is in development still and being actively worked on. I have asked the team for a more updated estimate when available and I'll share it here. 

[Rafal]

@Katie Silver any progress there or you maybe may share the link to this delivery, we may check the status?

[Katie Silver]

@Rafal I have excellent news for you! We are going to start the release of this on Monday and hope to have it out to 100% on Wednesday barring any issues. Will post here as soon as it's done. 

[Rafal]

@Katie Silver it seems it is not yet :(
is it to be tracked here: [AUTO-1219] Add support for compass components in Jira Cloud Automation - Create and track feature requests for Atlassian products.?

[Katie Silver]

We're currently at 10% - there was one small issue we had to fix so we are on track for this being at 100% by Friday morning US time. Thanks for the link - we'll update that ticket once it's out!

[Ken Young]

Thanks for the implementation of this new feature.

qq @Katie Silver .  Is there any guidance on how to to use the "additional fields" capability when creating or updating issues?

I haven't experimented yet but guessing that the following is preferred?

{
   "fields": {
      "components": [
          "newcomponent1",
          "newcomponent2"
      ]
   }
}

Thx

[Ken Young]

@Katie Silver 

When I try the following in additional fields (with the name of component registered in Compass), it tries create a new component in the project (which is linked to compass) instead of linking to the compass component:

{
   "fields": {
      "components": [
       {"name":"component1" }
     ]
   }
}

I tried to insert the ari for the component, but the additional fields entry resulted in an error that only name or id was accepted.

Thx 

[Katie Silver]

hey @Ken Young thanks for the feedback. We are still only at 50% rollout; it looks like your site may not have it yet. I'll also ask an automation team member to take a look at your questions since they know more than me!

As an update for everyone - we found another bug so it's currently looking like Monday. Appreciate your patience on all of this. 

[Ken Young]

Thx @Katie Silver .   When I saw the compass components in the create issue automation, I assumed it was deployed to our site.   Thx again.

[Rebecca Smith]

Hi @Ken Young - thanks for your questions! I'm from the Automation Product team, working closely with @Katie Silver

In response to your questions above;

1. You're exactly right - the syntax you've shared is preferred. There's also this Support doc if you haven't seen it already: https://confluence.atlassian.com/automation/advanced-field-editing-using-json-993924663.html

2. Looking into this, I think the issue you're experiencing is the result of a bug we found during the rollout. This should be resolved on Monday, and you should no longer continue to receive the error. 

We'll keep you updated, but in the meantime, if you have any further questions, please let me know. 

Thanks,

Bec 

[Ken Young]

HI @Rebecca Smith .   I was just wanted to followup to see the changes were rolled out.  

I tried this information in the extras field to dynamically assigned the component and it created a jira component instead of linking to compass component (of the same name)

{
   "fields": {
     "components": [
       {"name":"componenta" }
     ]
   }
}

Thx

[Ken Young]

Hi @Rebecca Smith or @Katie Silver . 

I wanted to follow up to see if the changes to components automation update (using the extras field) had rolled out?  If it is better to get updates via a public Jira ticket, please let me know.  Sorry to be persistent on this thread.

Thx

[Rafal]

It Works!!! ✨🎉❤

[Rebecca Smith]

Woo hoo @Rafal !!!!!