-
Bug
-
Resolution: Unresolved
-
Low
-
Severity 3 - Minor
-
Issue Summary
When creating a custom field via a connect app and setting it's value as link (using a template), the content of this field is not displayed as a hyperlink, whereas in old view this same field value is a clickable link.
Steps to Reproduce
- Create a custom field with a "link" template via a connect app.
- Follow the instructions in https://developer.atlassian.com/cloud/jira/platform/getting-started-with-connect/ to set up the app
- In atlassian-connect.json, have code to make a link field
- You do not need the HTML file, as the custom field should appear as a field that you can add from Project Settings to an Issue Type
- create a snippet in Source in the Dev Console to generate options
- Use https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-custom-field-options--apps-/#api-rest-api-3-field-fieldkey-option-post 's code to create options for the field
- Look at the graphql request to adjust the code to meet your context
- Populate the value with an option
Expected Results
The field value is a clickable link
Actual Results
The field value is a label-like value
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- derived from
-
JRACLOUD-74467 Add hyperlink for custom fields - link to search result returning all issues with that value
- Gathering Interest
- is related to
-
JRACLOUD-76802 In the new issue view, in a multi-line text custom field or in the issue description field, not all the URLs are rendered as links
- Gathering Impact
-
JRACLOUD-75883 Allow select list custom field options to be hyperlinks
- Closed
- is resolved by
-
ONECLOUD-3602 Loading...
- mentioned in
-
Page Loading...