Prefilling the Create New Issue page form fields from custom URL attributes
Problem to solve
If I want to send people to a New Issue page, there is no way for me to pre-fill the URL by the help of URL attributes. Challenge is, I work on a monorepo and I want to put the package's name on an issue title.
Description templates (https://gitlab.com/help/user/project/description_templates) are not the solution because in monorepo scenario, I want to manage DIFFERENT PACKAGES under the SAME REPOSITORY.
This means, we need a way to customise New Issue Title depending on which link customer clicked.
For example, this link below would instruct me that the issue is regarding the package array-group-str-omit-num-char
:
https:/gitlab.com/codsen/codsen/issues/new?title=array-group-str-omit-num-char%20package%20-%20put%20title%20here
For your reference, the Monorepo is here: https:/gitlab.com/codsen/codsen/
PS. BitBucket already has this feature, it can pre-fill New Issue fields from URL (not only some fields in the form, not all).
Target audience
- Monorepo library owners
- Audience of monorepo users
- People in general, who want to pre-fill the new issue form URL's
Further details
n/a
Proposal
Read and disinfect incoming URL attributes, then use them to pre-fill Create New Issue form fields.
For example, instead of currently limited URL, https://gitlab.com/<user>/<repo>/issues/new
, we should recognise title
and description
, in URL format like this: https://gitlab.com/<user>/<repo>/issues/new?title=The%20name%20of%20the%20title
.
The more Create New Issue form fields we can customise via URL's the better.
What does success look like, and how can we measure that?
If we can pre-fill the new issue forms passing custom URL attributes that would be success. For example, this pre-filling should work: https:/gitlab.com/codsen/codsen/issues/new?title=array-group-str-omit-num-char%20package%20-%20put%20title%20here
Links / references
See BitBucket, they have some of the fields pre-fillable but not all. If we could pre-fill ALL the New Issue fields and documented this, we would be ahead of BitBucket.
cheers.