ghost
commented
4 years ago This is a valid issue URL for SLES 15 SP1: https://jira.suse.com/secure/CreateIssueDetails!init.jspa?pid=18892&issuetype=9&summary=flub+flab&description=o+no&customfield_17225=24482&customfield_17203=****&customfield_17202=****&customfield_12302=wurscht+gwasn
- The product ID (e.g. 18892 = "SLE") it is best to find out via the API (so I just wrote jiracek), otherwise you need to pick apart Jira's ugly issue-page HTML
- Same for the version ID (e.g. 24482= "SLES 15 SP1"), and jiracek does this too
- Same again for the issuetype.
- You can't actually assign an assignee, but you have to choose a product/project manager (customfield_17203, customfield_17202), at least in the SLE project, may be different for other projects; luckily usernames are just usernames; the product/project managers must actually have that role assigned in Jira
- For SLE Epics, you need to have an Epic Title (customfield_12302) in addition to the Summary, slightly redundant.
In any case, the variability of all of this does not really fit into our model well. CaaSP needs completely different custom fields than SLE does, for example, in CaaSP, you must set a worker and a component and the version numbers need to be specified in the standard versions field instead of customfield_17225 .
SOC team would like to be able to open Jira issues via the Report Bug links.
cf. https://confluence.atlassian.com/jirakb/creating-issues-via-direct-html-links-159474.html