Create a custom button or custom link on issue view

[MrUpsidown]

Been searching on that topic for HOURS but couldn't find a single suitable solution. What I am after : I need a custom HTML BUTTON or custom HTML LINK that when clicked, will open a new browser tab and follow that link.

What I have tried : Jira built-in URL Field. It works but it's just SUPER UGLY as the entire link just displays and it seems there is no way to display the link as a standard HTML <a> element. My link is a long URL string with lots of parameters so I get something like

https://api.mywebsite.com/intervention/add?id={{issue.key}}&param1=ABCD&param2=EFGH&param3=JKLM&param4=NOPQ&hash=e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

Which obviously is TERRIBLE in terms of user experience.

Then I found several articles saying I should create a WEB ITEM with Scriptrunner but after reading dozens of documentation pages, I found out that WEB ITEM is NOT available on Jira CLOUD (only on Server).

So is there really no way to create a SIMPLE HTML LINK or a SIMPLE HTML BUTTON to just open an external link???

[Nic Brough -Adaptavist-]

It depends on what you mean by "state".

You could have that as a resolution option (so when a user closes an issue, they select "resolved by user" as the reason they're closing it)

You could build it into your workflows as an end status as well.

Or do you mean something else?

[Joe Stewart]

Thanks for the quick reply Nic. I probably used 'state' incorrectly but i was unsure of what to classify it as. I'll lay out my current example im trying to work through below, but i know there have been instances over the past few years where this has also come up internally as 'useful option' 

1. Team member transitions an issue into a resolved state because they feel they solved the issue
2. QA (or similar) determine the issue is not resolved and needs to be re-opened
3. We set the issue to Re-Opened (an custom field we created)
4. When setting this issue to "Re-Opened" i would like to automatically assign the issue back to the person who resolved it
5. I attempt to edit the workflow by adding a post function to automatically handle the re-assigning

This is the point where i cannot find a way to get the issue back to the person who resolved it. My hope was to solve this issue (and others that may arise) by finding or creating a "Resolved By" state/field/option. Thats where i get stumped. 

I think there are more practical applications for this then my specific flow, this just happens to be whats blocking me at the moment. 

Thanks again for the help