Platform Contributor Guide
[Legacy v3] Platform
[Legacy v3] Platform
  • 👋[Legacy v3] Welcome | README
  • Contributing | Getting Involved
    • Specific tasks needed for COVID19-support
    • Add code to Ushahidi
    • Encouraging contribution from non-developers
  • Frequently Asked Questions
  • Join the Ushahidi community
  • Contributors ✨
  • 🛣️ The Ushahidi Platform Roadmap
    • V2-V3+ Migration tool
  • Privacy and security best practices
    • Security as a user
    • Security for deployment admins
    • Security for deployment hosts
  • Development & Code
    • Development: Overview
    • How to get the source code
    • Setup Guides
      • Installing for production environments
      • Development environment with XAMPP
      • Development environment setup with Vagrant
      • [Client] Setting up the Platform Client for development
        • Migration from AngularJS
      • Setting up the Pattern Library for development
      • [API & Client] Bundled release install
    • Add code to Ushahidi
    • Development process
    • Coding Standards
    • Track and submit issues in Github
    • Upgrading Ushahidi
      • Upgrading to latest release
      • Upgrading from V3.x.x to V4.x.x
    • ⚙️ Installation Helper‌
  • Tech Stack
    • API Documentation
    • Third party app development
      • Web hooks
    • Database | Tables overview
    • Database | Database Schema Diagram
    • Database | Table details
    • 📐Architecture
    • Use case internals
  • QA & Testing
    • The QA process
    • How to run QA tests
    • Defect Management
    • How to write QA test scripts
    • Hotfixes
  • Front-end development
    • Changing UI styles: introduction to the pattern library
      • File-structure
      • Installing new packages
      • How to Apply to the Platform
      • Using the changed styles in platform-client
      • Syntax and Formatting
      • Grid, Breakpoints, & Media Queries
      • Variables
      • Mixins
      • Helpers
      • Icons
      • Create a New Component from Scratch
      • Read Direction
  • Design
    • 🎨Design: overview
    • 'Best practice' design
    • Ushahidi Platform 'Sticker Sheet'
    • User testing process
    • User testing script examples
    • Synthesising user testing results examples
      • Synthesis example 1
      • Synthesis example 2
      • Synthesis example 3
      • Synthesis recommendations example 1
      • Synthesis recommendations example 2
    • Open Source Design
  • Documentation
    • Documentation
    • Contributing docs via GitHub
  • Translation
    • Localization and Translation
  • The Ushahidi Platform Facebook bot
    • The Facebook bot
      • Installing the bot
      • The bot script
  • Hackathon and events
    • Installathon, May 2019
      • Welcome to the hackathon!
    • Write/Speak/Code 2019
    • Open Design: Bangalore
    • Open Design: Taipei
    • 📑Google season of docs
    • 💻Google Summer of Code
      • GSoC 2024
  • Enhancement Proposals
    • Exchange Format
    • Importing data from previous versions
Powered by GitBook
On this page
  • Track issues in Github
  • Submit issues in GitHub
  1. Development & Code

Track and submit issues in Github

All tasks are filed as issues in github.

PreviousCoding StandardsNextUpgrading Ushahidi

Track issues in Github

We log all our issues concerning development and documentation for the Ushahidi Platform in the . Issues marked with are issues that are up for grabs for any community-member.

Submit issues in GitHub

To submit issues in GitHub for the Ushahidi Platform, please go to and click on the "New Issue" button, or follow .

You will see a list of options for which type of issue you'd like to submit. The options:

  • Bug report: If you want to report something that is broken or not working as intended, please file a Bug Report. A good bug report is descriptive and reproducible.

  • Feature/enhancement request: Suggest an idea for a new feature or a small enhancement to existing features. This can be something as big as "Add a new way to import data into the Ushahidi Platform" or as small as "Change the font size of the login button to make it easier to use".

  • Epic level spec: this is only used when you want to create a very large request that encompasses multiple tickets and is likely to require a lot of work. It is primarily used by the Ushahidi team to group work together and plan for it, so you can ignore it for now.

For each of the options, when you click it you will be taken to a screen where you can fill in answers to our questions to submit a new issue. Please take the time to fill in all the required fields, as this will increase the chances that your issue will be understood quickly by both staff and community members, and it will also help us triage it correctly.

Important: Do not add tags to issues unless you are a maintainer. A maintainer will tag issues during triage, and add any staff or community members that need to be aware of the issue immediately.

Once you have filled all the requirements for the issue to be submitted, you can click "Submit new Issue" and your issue will be created. This triggers a notification to one Ushahidi staff who will review it as soon as possible.

Thank you for reading our guide to submitting a new issue to the Ushahidi Platform. We look forward to hearing from you!

Platform-repository
Community-task
https://github.com/ushahidi/platform/issues
this link
New Issue button in GitHub
Screen Shot 2019-08-01 at 14 47 50
Screen Shot 2019-08-01 at 14 44 10
Screen Shot 2019-08-01 at 14 36 16