Introducing a New Automation Action - Add Web Link to Work Item 🔗

[#1]

Hey Atlassian Community,

I’m Raine from the Automation team, and I’m here to announce a new action to kick off 2026!

As your toolkit grows, managing all of your web resources can be a real challenge, and as a result, many of you have asked us for the ability to add web links to your automation rules.

Previously, you could only add web links to work items manually - which was great for single-use resources, but not so much for larger scale ones.

Now, you can add resources both ways! No more manual linking tedium - our action offers a simple, efficient way to add web links to your work items. However, please keep in mind that a limit of 2000 remote links exist on work items.

What this new action looks like:

And, smart values boost your capability where manually adding web links can’t:

With this new action, you can add web resources to your work more efficiently than ever. We’re excited to see how you’ll use this component and would love to hear your feedback below!

[Alex Koxaras -Relational-]

That will be handy!

[William (Bill) Klein]

Nice, thank you!

[Dirk Ronsmans]

Great one! no longer need to do this with a "send webrequest" :)

[Edie Hovermale]

Great to see more functionality coming to Automation. So many of my customers have asked for this! Yay!

[Rick Westbrock]

I don't see this action in JSM Operations automation rules, is that part of the rollout? If so what is the rollout timeframe?

[Raine Gu]

Hi @Rick Westbrock, thanks for your comment! We are progressively rolling this action out to our different products and it should be in JSM Operations by the end of this week. We'll let you know when it's ready to go!

[Chris Rogers]

Hi @Raine Gu 

Are there limitations to how this new action is used?  I tried using it this morning, but adding a smart value to the link (e.g. https://clientsite.atlassian.net/browse/{{Client Issue Key}}); however, Automation wouldn't let me save the rule.  Validation gives the following error:

The component itself doesn't show an error, and if the smart value is removed, the rule appears to save without issue.

[Dirk Ronsmans]

We have the same issue as @Chris Rogers

The action seems to work unless you add a smartvalue. Either the rule doesn’t save and /or validation throws an error. 

[Raine Gu]

Hi @Chris Rogers and @Dirk Ronsmans! Thanks for bringing this to our attention!

Yes, currently our action's link field is limited to receiving either a smart value or plain text. There is a workaround for compound links (e.g.https://clientsite.atlassian.net/browse/{{Client Issue Key}}) where you can first assign the compound link to a smart value with our "Create variable" action. Then, pass that new smart value into "Add Web Link to Work Item".

Please see these images for a more detailed example, with a compound link that evaluates to https://www.example.com:


We understand this might be a frustrating workaround, and are actively looking into extending support for compound links! Thanks for your feedback.

[Chris Rogers]

@Raine Gu thank you for the workaround and quick response; that'll work for the time being!

That being said, it would be helpful to have a more informative error message on why that's occurring :)

[Dirk Ronsmans]

Thanks @Raine Gu ,

It's not the first action that requires an intermediate variable for it to work.

Might need to make sure the error/validation provides something proper tho ;-)

We'll use the workaround for now! Appreciate the quick response.