Goal: 
Create new issue(s) for follow-up tasks from an existing issue. Background: In most projects in the Drupal community, we try to keep issues limited to one topic. Often, during development or just before the commit for an issue, new topics come up that need to be addressed. Rather than address them in the original issue, we usually prefer to open new issues for each follow-up topic.
Skills required: 
Technical writing (English)
Background and reference information: 
Find the issues for a project
Creating or updating an issue report
Issue tags field
Detailed steps: 
  1. Set up prerequisites: Log in from Common Prerequisites for Contributors.
  2. Choose a project to work on, either Drupal core or a contributed module, theme, or distribution that you are familiar with and find the issues for the project.
  3. Search for issues with tag "Needs followup" -- use this link to search Drupal core for the tag, or learn more about searching for issues.
  4. Select an issue to work on. Read the issue summary and make sure you understand it. If not, find a new issue.
  5. Determine what follow-up issues are needed:
    • They could be listed in the Remaining Tasks or Proposed Resolution section of the issue summary.
    • If not, use your browser's Search function (control-F, command-F, or similar) to find the comment where the Needs followup task was added to the issue. Hopefully, this comment will describe the follow-up tasks.
  6. For each follow-up issue that is needed, see if the issue has already been created by looking at the Child issues and Related issues sections of the sidebar. You can also search the project's issue list for keywords to see if the issues already exist.
  7. If one or more follow-up issues need to be created, for each:
    • Click either the "Add child issue" or "clone issue" link in the sidebar. If you clone an issue, you'll automatically have the same title, issue summary, status, and other values from the original issue (but not the comments). If you make a child issue, you will have an empty issue summary template and will need to fill in the values.
    • Edit the issue title and summary to describe the follow-up task. Make sure to include a link to the original issue, by inserting something like Follow-up to issue #12345: How do I log in as admin? at the top of the issue summary, replacing 12345 with the issue ID number (end of the issue URL)
    • Set the status, component, priority, and other issue values appropriately (see the Creating or updating an issue report page for details).
    • Save your new issue.
  8. At this point, all of the follow-up issues should either have previously existed or you created them. Update the original issue to list them:
    • If existing issues were not already listed as Child or Related issues, add them to the Related issues in the Issue Summary & Relationships section of the issue (see Creating or updating an issue report for more on updating issues). If you created the issues in the previous step, they will automatically be listed as Child issues, so skip this.
    • Add a section to the Remaining Tasks section of the original issue summary listing the follow-ups, if there isn't one already, and make sure this section links to all the issues. To make a link to an issue, insert #12345: How do I log in as admin? into the text of the issue summary, replacing 12345 with the issue ID number (end of the issue URL).
    • Remove the "Needs followup" issue tag.
    • Add a comment to the issue saying that all of the follow-up issues have been created, and save the issue.