Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Component/s: tracker.moodle.org
    • Labels:
      None
    • Rank:
      38678

      Activity

      Hide
      Martin Dougiamas added a comment -

      I just did a little cleaning up of the issue creation screen for bug reporting, by removing testing instructions and sorting the fields more logically.

      Show
      Martin Dougiamas added a comment - I just did a little cleaning up of the issue creation screen for bug reporting, by removing testing instructions and sorting the fields more logically.
      Hide
      Martin Dougiamas added a comment -

      then I removed a couple more fields ...

      Show
      Martin Dougiamas added a comment - then I removed a couple more fields ...
      Hide
      Helen Foster added a comment -

      I think the create issue screen looks tons better now, thanks Martin!

      Just one thing I didn't understand though: the phrase "or press down to select." Did you mean "or click the down arrow"?

      Show
      Helen Foster added a comment - I think the create issue screen looks tons better now, thanks Martin! Just one thing I didn't understand though: the phrase "or press down to select." Did you mean "or click the down arrow"?
      Hide
      Martin Dougiamas added a comment -

      Unfortunately that phrase is inserted by Jira on those types of fields. It's out of our control.

      Show
      Martin Dougiamas added a comment - Unfortunately that phrase is inserted by Jira on those types of fields. It's out of our control.
      Hide
      Helen Foster added a comment -

      Also, I'm not sure whether we need "This is important to help us find the right person to deal with it." Obviously the field is important as it's required and we don't want to make people feel worried if they can't find an appropriate component for their issue.

      Show
      Helen Foster added a comment - Also, I'm not sure whether we need "This is important to help us find the right person to deal with it." Obviously the field is important as it's required and we don't want to make people feel worried if they can't find an appropriate component for their issue.
      Hide
      Martin Dougiamas added a comment - - edited

      I've simplified the default front page considerably, and written better intro text. About the component - doing it correctly really helps everyone ... I think it's important to say.

      Show
      Martin Dougiamas added a comment - - edited I've simplified the default front page considerably, and written better intro text. About the component - doing it correctly really helps everyone ... I think it's important to say.
      Hide
      Helen Foster added a comment -

      Just noting here that I've turned off incoming trackback pings, as I noticed they were being used for spam.

      Show
      Helen Foster added a comment - Just noting here that I've turned off incoming trackback pings, as I noticed they were being used for spam.
      Hide
      Michael de Raadt added a comment -

      I'm no longer seeing people providing replication steps any longer. I'm having to prompt a lot of people.

      Show
      Michael de Raadt added a comment - I'm no longer seeing people providing replication steps any longer. I'm having to prompt a lot of people.
      Hide
      Helen Foster added a comment -

      Just noting that Michael and I had a chat about people no longer providing replication steps.

      Michael said he voted for keeping testing instructions in the create issue form, as people were incorrectly using it for replication steps, which was then easy to copy over.

      It seems a lot of new people have been reporting issues, which is good, but if Michael has to comment asking for replication steps and half of the time people don't respond, then it's not very productive.

      Unfortunately people don't notice/ignore the text about the description field (currently 'Please include: FULL STEPS that developers should take to reproduce the problem, as well as information about WHAT YOU EXPECTED and WHAT ACTUALLY HAPPENS for you.') and Jira doesn't allow for the text to be positioned above the description field, or for the description field to be renamed.

      My thinking is that reporting issues is one area in which the community can really help a lot, so we should encourage is as much as possible, and keep the create issue form simple and inviting. I thought perhaps we could run a publicity campaign encouraging people to report issues in the tracker and stressing the need for steps to reproduce. It could be that not providing replication steps is just a temporary problem due to lots of new people starting to report issues, and further guidance will result in people remembering to include them in future.

      Show
      Helen Foster added a comment - Just noting that Michael and I had a chat about people no longer providing replication steps. Michael said he voted for keeping testing instructions in the create issue form, as people were incorrectly using it for replication steps, which was then easy to copy over. It seems a lot of new people have been reporting issues, which is good, but if Michael has to comment asking for replication steps and half of the time people don't respond, then it's not very productive. Unfortunately people don't notice/ignore the text about the description field (currently 'Please include: FULL STEPS that developers should take to reproduce the problem, as well as information about WHAT YOU EXPECTED and WHAT ACTUALLY HAPPENS for you.') and Jira doesn't allow for the text to be positioned above the description field, or for the description field to be renamed. My thinking is that reporting issues is one area in which the community can really help a lot, so we should encourage is as much as possible, and keep the create issue form simple and inviting. I thought perhaps we could run a publicity campaign encouraging people to report issues in the tracker and stressing the need for steps to reproduce. It could be that not providing replication steps is just a temporary problem due to lots of new people starting to report issues, and further guidance will result in people remembering to include them in future.
      Hide
      Mary Cooch added a comment -

      I do understand both points of view here-it must be very frustrating if you want to check an issue and don't have any replication steps but I also feel it is very off-putting for newcomers who will be afraid they might not set the steps out correctly or not know how to "phrase them". If we do a publicity campaign (which is a good idea) it might be helpful to provide some simple examples of replication steps so people have an idea what they should do.

      Show
      Mary Cooch added a comment - I do understand both points of view here-it must be very frustrating if you want to check an issue and don't have any replication steps but I also feel it is very off-putting for newcomers who will be afraid they might not set the steps out correctly or not know how to "phrase them". If we do a publicity campaign (which is a good idea) it might be helpful to provide some simple examples of replication steps so people have an idea what they should do.

        People

        • Votes:
          0 Vote for this issue
          Watchers:
          4 Start watching this issue

          Dates

          • Created:
            Updated:

            Development