STELLA: Knowledge Based Articles

    Stay up to date with our most recent updates to that thingamujig we all use everyday.

      Submitting a Feature Request OR Bug/Issue

      Posted by Yoda on Nov 4, 2020 3:00:12 PM
      Yoda

       

       

      There are two types of support requests that you can submit:

      Feature Request: A feature request is requesting that net new functionality be added to the system. This could be something completely new or it could be an enhancement to existing 

      Go to how-to

      Incident/Issue/Bug: You would submit a bug/incident ticket when existing functionality is not working as it is intended to work.

      Go to how-to

      New Article: If there is functionality or a topic that you would like a tutorial/educational article to reference, submit a request for the article to be created.

      Go to how-to


      Feature Request

      1. Navigate to the Support Request entity in Stella
      2. Select 'New' in the tool barimage-png-Nov-04-2020-07-34-25-47-PM
      3. On 'Support Type', select 'Feature Request or Suggestion'
      4. Pick the 'Severity Level' - this is your opinion of how important what your submitting is. Your options are Low, Medium, High and Critical. Something 'low' might be something that would maybe save you a click or a few seconds, but not necessary to do your job. Something 'critical' might be something that we don't have but we absolutely need immediately in order to continue to effectively provide service to customers and pay pros.
      5. Submit a brief summary of the request:
      6. the Tech Team Response section is not something you need to fill out; this is where the tech team will update the status of the feature requests to keep you updated
      7. Fill out the 'Audience Impacted by Issue or Feature'
      8. Fill in the 'Request Type'
        1. New feature of functionality
        2. Change to existing feature of functionality
        3. change to data or information
      9. Fill out request area accurately to tell us which entity or area of the system you're looking to enhance
      10. Feedback description - this is where you explain what exactly you are requesting. Use as much detail here as possible. The more detail we have about what you're wanting, the faster we can make a decision. Example of things to include:
        1. Where in the system?
        2. Record type?
        3. Fields you want?
        4. Automation?
      11. Feedback Justification - this is where you tell us why this would be impactful the system and enhancing work experience. This is your area to build a business case as to why we need to spend the time to complete the requested feature request.

      Incident/Bug

      1. Navigate to the Support Request entity in Stella
      2. Select 'New' in the tool barimage-png-Nov-04-2020-07-34-25-47-PM
      3. On 'Support Type', select 'Incident or Issue'
      4. Pick the 'Severity Level' - this is your opinion of how important what your submitting is. Your options are Low, Medium, High and Critical. Something 'low' might be something that would maybe save you a click or a few seconds, but not necessary to do your job. Something 'critical' might be something that we don't have but we absolutely need immediately in order to continue to effectively provide service to customers and pay pros.
      5. Submit a brief summary of the request:
      6. the Tech Team Response section is not something you need to fill out; this is where the tech team will update the status of the feature requests to keep you updated
      7. Fill out the 'Audience Impacted by Issue or Feature'
      8. Fill in the 'Incident or Issue Type' from the dropdown optionset
      9. Fill out corresponding 'Type'
        1. Software type options:
        2. Hardware type options:
        3. Service type optionsL
        4. Rent Ready Data type options:
      10. Reproduction Steps - this is where you explain to us what steps you took to come across the issue so that we can trouble shoot the issue. Things to include:
        1. What record type were you on?
        2. What did you click? 
        3. If there is more than one way to get to the page where the issue is, how did you get there?
        4. What other fields did you update?
      11. Issue description - this is where you tell us what went wrong. What happened that wasn't supposed to happen or what didn't happen that was supposed to happen.

      New Article

      HubSpot Video