Skip to content

Link to open an issue from a failed Build with pre-filled details #3539

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
humitos opened this issue Jan 22, 2018 · 11 comments · Fixed by #3683
Closed

Link to open an issue from a failed Build with pre-filled details #3539

humitos opened this issue Jan 22, 2018 · 11 comments · Fixed by #3683
Labels
Accepted Accepted issue on our roadmap Good First Issue Good for new contributors Improvement Minor improvement to code

Comments

@humitos
Copy link
Member

humitos commented Jan 22, 2018

There are several issues that are reported where there are missing information in the details section.

To solve this I was thinking on generating a link inside this message that could contain all the information pre-filled:

captura de pantalla_2018-01-22_15-07-15

I found that github supports some query arguments in the URL but I didn't found a way to use those key/args inside the template itself.

https://help.github.com/articles/about-automation-for-issues-and-pull-requests-with-query-parameters/

I think it would be awesome if the user can just click a link and the username, project url, etc could be pre-filled automatically.

@humitos humitos added Improvement Minor improvement to code Good First Issue Good for new contributors labels Jan 22, 2018
@RichardLitt
Copy link
Member

Could you not have the link generated with that information in the body tag?

@humitos
Copy link
Member Author

humitos commented Jan 22, 2018

Yeah, maybe.

The template is 227 chars long, if we add the project and build link plus username I'm not sure if we are not creating a too long URL that it's not standard. I know there is a limit and I think it depends on the browser also...

https://stackoverflow.com/questions/417142/what-is-the-maximum-length-of-a-url-in-different-browsers

We could do that since the limit is around 2000 chars.

@agjohnson
Copy link
Contributor

Neat idea. We need to make sure wouldn't show on the .com though, as we don't want github issues for those issues.

@stsewd
Copy link
Member

stsewd commented Feb 11, 2018

What about putting this information on the header of the raw build log (see #3585)? So the user can just referrer that link or copy/paste the raw log on the issue.

@bansalnitish
Copy link
Contributor

Hi @humitos, May I work on this!

@RichardLitt
Copy link
Member

@bansalnitish It doesn't look like @humitos has opened a PR for this; he's only specified a need for it. I'd say go ahead! :)

@bansalnitish
Copy link
Contributor

Thanks @RichardLitt!

@bansalnitish
Copy link
Contributor

Hi @humitos, Can you please help me in reproducing this issue!

@humitos
Copy link
Member Author

humitos commented Feb 26, 2018

@bansalnitish hey! What you need?

The idea is to add a link in the build page (showed when it fails) that opens an issue in this Github project.

(there is a link to the GH docs to generate that link in the description)

@bansalnitish
Copy link
Contributor

I got it @humitos, Thanks! I will be soon submitting a PR for the same!

@stale
Copy link

stale bot commented Jan 10, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Status: stale Issue will be considered inactive soon label Jan 10, 2019
@stsewd stsewd added Accepted Accepted issue on our roadmap and removed Status: stale Issue will be considered inactive soon labels Jan 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accepted Accepted issue on our roadmap Good First Issue Good for new contributors Improvement Minor improvement to code
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants