Getting Started in the Issue Queue

We are here going to know how to report the issues in the Issue Queue and for that we should know how to report an issue, confirm a bug report. 

So, here we are going to post a sample issue , and it can be done in following manners -

1. Firstly, go to the Drupal 8 Sandbox issue (The issue is a sample issue which is used to make beginners understand issue queue.)

 

2. Then ,Under Component, select Miscellaneous and under Category select Bug Report. 

3. Now , Copy the following text and paste it into the title Box.  

Rewrite description for URL alias on node/add/*

4. Then , Copy the following and paste into the Description Box : 

Note: This issue is being posted here as an exercise by a participant in the http://drupalladder.org ladder for contributing to core. Please don't do anything with this post. The real issue has already been resolved in Drupal 8. If you would like to try this exercise yourself, visit http://drupalladder.org and click on Drupal Ladder

Current:
Optionally specify an alternative URL by which this content can be accessed. For example, type "about" when writing an about page. Use a relative path and don't add a trailing slash or the URL alias won't work.
Proposed:
The alternative URL for this content. For example, type "about" when creating an about page. Use a relative path without a trailing slash

5. After completing the above steps, hit save and you will see that your issue has been posted.

 

6. After  we have created the issue, we have to confirm a bug report which can be found in the Drupal Sandbox Project which can be installed by typing the following command :

git clone --branch 8.x https://git.drupal.org/sandbox/bhirsch/1388780.git drupal_8_sandbox_for_drupal_ladder

7. After you have installed your sandbox project, move to your sandbox site, and the bug (which is help text to make an URL alias is bit confusing) can be found under Add content -> Article or Basic Page -> URL Path Settings . If you found the bug, the confusing text, there, then you can comment by posting a screenshot of it on your issue, thereby confirming the bug. 

 

8. For that, Go to the issue which you have posted and then click on Comment.

Then, you can comment how the bug can be found and can attach the relevant screenshot ( I have attached the above screenshot).

The comment can be made like this :

 

9. So, Congratulations, the bug report has been confirmed. Now , the last thing to do is to update the issue summary which can be done according to Drupal .issue summary template And it will look like this after updating the issue summary:

 

 I learned a lot of basics, when I did it, like how to find the issue, how to reproduce the bug and I also learned to show the thing that the other active users need to fix in the issue. 

I will continue to utilize these skills in future too by finding more issues and will continue dealing with the issues to become an active user in the Drupal Community!