BONUS: 5‌ CHECKPOINTS AWARDED WORTH ‌$100‌ EACH

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to “Issue Tracking Grading Web Application Wireframes”. Our client wants to build a web application that merges ticket from 2 issue tracking tools (JIRA and RALLY) and provides an automated grading and report.  In this contest, we need your help to create application flow using our document requirements provides in this contest. The requirements them selves are quite simple and straight forward.

At the end of this contest, we are looking an HTML wireframes which showing a new workflow solution for our problems, provides great user experience for the application and can be used as suggestion for the next development phase. Join Now!!

 

Round 1

Initial wireframes solution for client review

Round 2

All contest requirements as stated in contest details with client feedback applied


 

Our client is the largest cable’s company in the US and would like to build a web application that merges tickets from 2 issue tracking tools and provides an automated grading and report. The 2 issue tracking tools are JIRA and RALLY.

This project purpose is to pull out JIRA and Rally tickets and and push them out to webpage for everyone to see,  then, using some formula (will be define in next phase) and based on the feedback, it would be graded accordingly. They already have their own system of grading and now they want to grade it automatically. They want a crawler for JIRA for Rally and bring it down to a webpage.

Attached in this contest is a PDF version (mock ups) of the last report we manually generated for a project. What our client wants is something close to this that configurable to add and remove data depending on the project. See below for additional details :


1.    PAGE 1 - Index Page
- They want the first page configurable on their side. There are links on this page that link out to the specific projects.
- List of projects team and qa leads
- Project will come either Rally or Jira and will ned to be configured
- Team name and QA Lead will be manually entered

2.    PAGE 2 - Current Grade Page
- is the score itself, we wants it to have a textbox to post QA comments and to link out to different website. They only ship for A & B grade.
- Current project grade
- The current grade is based on the highest lvl severity bug that is currently open. For example a Sev 1 counts as an F and that will give the overall project a grade F
- Sev 1 : F, Sev 2 : C, Sev 3 : B. Sev 4 : A -- If no bug are open the project gets an A+
- There is a possibility of adding extra grad levels (+,-) in the future so if possible the classification of bugs based on sev level should be configurable
- This page must have a editable text area for QA Comments
- This page will have links to the other grade pages (if any exist, if the grade is an A+ there are no links present)
- This page will have a link to the grade classification page
- This will link to an appendix page (future addition)

3.    PAGE 3-6 - Grade Page
- Bug listings per grade level
- Each page will contain a link back to the grade page, a link back to the main project page, and a link to the next bug listing page if appropriate
- give examples of the layout for the grade pages, Each bug has priority and summary that you can pull form the JIRA API. They want a clickable link to the bug itself.

4.    PAGE 7 - Grade Classification
- how they grade
- Grade page lists the severities and their associated grade

5.    PAGE 8 - Bug Classifications (Selection page not included in mocks)
- Tags are inserted into bug summaries, we would like a page that the user can select different tags and generate a listing of all bugs containing the tag(s) in it's summary
- Dynamically generate pages that list different classifications of bugs in different combinations
- Currently used tags [iOS], [Android], [Functional], [Performance], [UI]
- New tags should be able to be interred via config
- is the most complicated, they use tags and brackets to label and list out bugs. They want the ability to proactively to scan for each tag and pull out functional bug based on tags. Needs to be dynamically generated based on the tags they pull in.

Notes :
-    One view for all users – no admin view
-    They want a report that’s constantly updated so the team can go to the web page and see what the grading is so far. They can do that today but it’s complicated to do so they want it automated and displayed automatically.
-    They want a website and crawler set up to pull the information from the 2 issue tracking tools for the users to navigate to.


Target Audience
This application will be used by Internal Employees of client company
 
Judging Criteria
Your submission will be judged on the following criteria:
-    User Experience
-    Completeness and accuracy of the solution to solve client problems.
-    How well your wireframes provide a consistent user flow


Submission & Source Files
Preview Image
Create your preview image as one (1) 1024x1024 JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.

Submission File
Generated HTML files with all the requested contest requirements stated above.

Source Files
Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.

Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.

 

Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.

Stock Photography

Stock photography is not allowed in this challenge. All submitted elements must be designed solely by you. See this page for more details.

How To Submit

  • New to Studio? ‌Learn how to compete here
  • Upload your submission in three parts (Learn more here). Your design should be finalized and should contain only a single design concept (do not include multiple designs in a single submission).
  • If your submission wins, your source files must be correct and “Final Fixes” (if applicable) must be completed before payment can be released.
  • You may submit as many times as you'd like during the submission phase, but only the number of files listed above in the Submission Limit that you rank the highest will be considered. You can change the order of your submissions at any time during the submission phase. If you make revisions to your design, please delete submissions you are replacing.

Winner Selection

Submissions are viewable to the client as they are entered into the challenge. Winners are selected by the client and are chosen solely at the client's discretion.

ELIGIBLE EVENTS:

2014 TopCoder(R) Open

Challenge links

Screening Scorecard

Submission format

Your Design Files:

  1. Look for instructions in this challenge regarding what files to provide.
  2. Place your submission files into a "Submission.zip" file.
  3. Place all of your source files into a "Source.zip" file.
  4. Declare your fonts, stock photos, and icons in a "Declaration.txt" file.
  5. Create a JPG preview file.
  6. Place the 4 files you just created into a single zip file. This will be what you upload.

Trouble formatting your submission or want to learn more? ‌Read the FAQ.

Fonts, Stock Photos, and Icons:

All fonts, stock photos, and icons within your design must be declared when you submit. DO NOT include any 3rd party files in your submission or source files. Read about the policy.

Screening:

All submissions are screened for eligibility before the challenge holder picks winners. Don't let your hard work go to waste. Learn more about how to  pass screening.

Challenge links

Questions? ‌Ask in the Challenge Discussion Forums.

Source files

  • HTML
  • RP file created with Axure

You must include all source files with your submission.

Submission limit

Unlimited

ID: 30036112