We are looking to introduce Jira (Jira Cloud) into our team to handle software development and third level support issues. In both cases we have a need to link the Jira issue to an external source.
For example, for third level support we have first and second level support handled using Salesforce Cases that are raised by the customer and managed by the support team. When we get to third level support, the Jira issue will be created by support, based on the Salesforce Case and we want to include the Case ID as part of these details. We then want to be able to generate a clickable link on the Jira issue screen that uses a defined base URL together with the value of our custom field holding the Case ID. It would have a URL incorporated into the page as a clickable link like:
<a href="https://myorgdomain.salesforce.com/{issue.fields.salesforceCaseID}">Salesforce Case</a>
I cannot find any out-of-the-box way to handle this. Have I missed something or does this truly require the creation of an externally hosted add-on?!
Sorry, I missed this first time around.
Jira has now way to know what you want to link to unless you tell it. Off-the-shelf, there's a simple solution - use a "url" type field and ask your users to put it in there. Or, better, ask them to use the "link" function (it's not just for linking to other Jira issues)
For what you've defined though, no. Atlassian do not do calculated fields (other than resolution date) because there's just too many possible things to cover and they only want to write generic functions that cover most or all options.
So, for something more advanced, you will need an add-on.
Personally, I'd use ScriptRunner (I would say that, I work for Adaptavist, but I would have said the same before I joined, and would still say it if I left).
And, in all cases, I'd probably incorporate validation that the other end of the link at least exists.
Thanks Nic.
My concern is verified - I would have to use an add-on (whether that was ScriptRunner or something else).
We use a full URL field for this because we had no choice; the addition of more cost to the licencing of Jira could not be justified. I think it is a shame they don't support even trivial "templating" of UI components. Indeed, the whole UI configurability is pretty limited IMHO. I can't chose the ordering of fields on the UI, for example. Quite disappointing.
Phil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Totally agree with this. Atlassian's inability to play well and integrate with other platforms has been quite the turn off... I can link a Jira ticket easily from a Salesforce Case, but not the other way around. :/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's because Salesforce doesn't provide a simple and easy API to allow Jira to connect and validate links, unlike Jira does.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
IMHO it feels much more like a case of making you pay for anything that is over and above the most basic functionality (which of course you are already paying for).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It does. And Salesforce is already horribly expensive. At those prices, you'd expect it to provide the basic hooks for other systems to connect and validate incoming links.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is as may be, but I still can't use a simple template with field substitution to create a link or other value in Jira Ui. That is what thisthread was aabout.i don't need to validate it. Just generate it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You'll need to take that up with the vendors of the systems you are trying to generate links for.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry mate but that is pure deflection. If I want to make a link, if the link has a specific format all I have to be able to do is specify the format and substitute in the required value. In this case I want to have the format deal with the host on which we have the customer-facing case so all we have to keep in the Jira is the ID. Why on earth do I need anything from the external system to have such capability. You talk nonsense.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, sorry, I misunderstood yesterday.
My answer from 2 years ago still stands for the way to construct data without going off to other systems. The reason Atlassian don't do it is that there's no way to code for every possible thing you might want to do, so the only option is to allow you to write code directly. But they don't want to have to support ad-hoc scripting that things like ScriptRunner and Powerscripts enable.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.
Register NowOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.