For improvement of the current issue tracker, the implementation of the task can be divided into 3 parts:

Currently the /+tickets view lists all the tickets with some options including few important

filters like "all", open, "closed" and "tags". Also, the current view consist of an option for creating a new ticket and a search box to find tickets. In this view, we can include an "Advanced Search" feature where we can add additional filters for filtering tickets based on a particular "author", "tags", "assignee", "difficulty", "effort", "severity" and "priority".

For "Advanced Search" option, a new view /+tickets/query will be created, where additional filters will be provided through which we will filter the results based in the query applied in the view: /+tickets?<query_type>=<query>. We will also allow to apply multiple filters in our advanced search.

Wireframe for ticket list view and advanced search view:

In the community bonding period, I reviewed my proposal again and discussed with my mentors about what features are necessary, how things should be implemented and cleared my doubts. I read the documentation, read the code to understand the flow of execution and how things have been implemented.

I learned about form processing using Flatland, and its really cool :) as explained in their website:

---

Flatland maps between rich, structured Python application data and the string-oriented flat namespace of web forms, key/value stores, text files and user input. Flatland provides a schema-driven mapping toolkit with optional data validation.

I allows DWIM (Do What I Mean) binding. Here is a run-of-the-mill example to explain:

>>> from flatland.out.markup import Generator
>>> from flatland import Form, String
>>> html = Generator()
>>> class Name(Form):
...     firstname = String
...     lastname = String
...
>>> form = Login({'firstname': 'Vipul'})

"Do What I Mean" binding:

>>> print html.input(form['firstname'])
<input name="firstname" value="Vipul" />

I also read about Jinja2 template engine,  a beautiful full featured template engine for Python. Having tried my hands on Django, I was a little familiar with Django template language which was also the inspiration for Jinja2. I read how macros work in Jinja2. Macros can be compared to functions in programming languages. Its a nice tool to promote DRY (Don't Repeat Yourself) principle while writing templates. The most often used elements can be written in a reusable function i.e. a macro which can be called like a function in the templates.

A small example to demonstrate how to render a form element:

    {% macro render_input(n, value='', type='text', size=20) -%}
        <input type="{{ type }}" name="{{ n }}" value="{{ value|e }}" size="{{ size }}">
    {%- endmacro %}

This macro can be called like a function:

    <p>{{ render_input('firstname') }}</p>
    <p>{{ render_input('lastname') }}</p>