sed 's/issue/need/g'

Replace all occurences of the word issue with need. This seems to be the common term in the humanitarian sector.

• Mobilversion
• Desktopversion

We currently have a single container component to handle issue details/ comments / comment posting.
The passing down of props is quite bothersome. I will have to refactor this to have multiple containers.

Just noticed that the password reset form is completely unstyled. It works but it's ugly.

twitter like mentions of users / organisations (@sos-kd, @msf, @hans) in comments and issue descriptions

The current state of the frontend build works quite nicely but could use some optimisations.

I am thinking of:

• hot module replacement
• better dev/production/test configs
• more npm scripts
• more documentation

The markers as used on the map are supposed to show icons referencing the issue type.
Since multiple issue types per issue are possible this is hard to do.

Enlarge Logo Toucan Logo: https://toucan.beetwo.at/

The add issue page is currently a plain django html page with form and s special js entry point for map selection. This should be part of the main interface.

Create an intermediary model between organisation and issue types.
Then allow organisations to configure which expertise they have, allowing them to add a few lines of text to specify the details.

We want to redo the issue creation form.
Issue creation should encompass the following steps:

1. Select a location. Either by selecting from a map or a list of locations defined by your organisation
2. Select the What of the issue/need:
   • medical assistance
   • supplies
   • demand
   • etc
3. Structured input of the needs, to be seen in conjunction with the What captured in step 2. e.g: medical assistance for 3 pregnant women, 1000 water bottles for our field supply camp

link to organizations, short text, areas of expertise, area of operation

There is currently no way to actually close an issue.
As a first step every signed in user should be able to close/re-open an existing issue.

It is currently not possible to change the email address once the user is registered.
The django allauth package allows this with some configuration and extra templates etc.
http://django-allauth.readthedocs.io/en/latest/views.html

• Add heading "Issue location"
• Add initial marker to map

Toucan is currently focused on requests for help.
In the future we might want to allow "issues" that offer help. This issue is here to discuss options for such a feature.

IMHO the easiest way to facilitate such a feature would be to create a issue type named 'offer' , but that could make it harder to integrate further workflow related to "offers" in the future.

Since we are not capable yet of sending notifications, we should disable the option for notification rules and add a message explaining that this will be possible in the future.

Anything that is more or less here is quite unstyled and outright ugly: https://toucan.brickwall.at/toucan/profile/

We need both a navigation concept ( see #91 ) and some more form styles.

Currently it is only possible to add a homepage and any number of locations to an organisation. The designs show multiple telephone numbers, email addresses etc.
I'll have to implement various fieldtypes to accomodate this.

From a mail from Isabella:

Uns ist nicht ganz klar wieso wir das entschlossen haben, man sollte nur Teil einer Organisation sein können.

Apart from the permissions (admin/member) inside an organisation, admins should be able to add job descriptions for their members.

e.g. "Camp Manager", "Logistics"

On the organisation page we should hide the "Become a member" button when the user is already a member of any organization.

• Learn more durch Download Factsheet ersetzen

We need to implement the icons from the attached pdf.
This issue tracks the progess on this.

170804_beetwo_toucan_category-icons.pdf

Mapbox (https://www.mapbox.com/) looks interesting and offers a lot of options to customize the look and feel of maps, might be an interesting approach to improve the mapping features

These are some open issues/feature requests that I will have to deal with in the next days.
Source: @fadr via slack

Toucan Progammierhilfe

• Add Need / I can pick it up by myself
  → eintrag in der db und display auf der issue detail seite (da mag vielleicht emanuel auch noch was dazu sagen)
  → einbau in die filter

• Issue Status (open/in progress/resolved)
  → db und verknüpfung mit dem dropdown auf der issue detail seite
  → dann kann auch der resolve button weg (da ist allerdings dann noch offen wie man eine resolve Nachricht eingibt)

• Kategorie
  → nur eine erlauben beim erstellen

• Filters
  → Labels sind jetzt die CSS Klassen
  → Reset sollte die Filter zurücksetzen (das kann man sonst auch erst mal ausblenden)
  → Beim Filter sollte eine Zahl mit der Auswahl daneben stehen wenn Filter ausgewählt sind

• Listen
  → Sorting ist noch nicht implementiert
  → Wenn man auf den MapHandle klickt sollte die Klasse .listExpanded an .app-container angehängt werden.

• Add meta tag

• Cancel buttons für Formulare
  → Sollte auf die vorherige Seite zurückspringen, wenn das geht?

Currently the marker colors are different from the colors used in the bootstrap theme. I think it would be a good idea to make the marker color equal to the color used by the status label. This way it would also be possible to distinguish open from closed issues on the map.

The server at https://b2it.brickwall.at/ does not serve user uploaded images (org logos etc)

It is currently not really clear how to input your phone number:

New solution/design suggestion for the "Return to Toucan" - Button

React state is somehow not cleared after writing a comment and then writing another one and opening/closing the issue during these actions.

provide a list of closed issues sorted by date closed in reverse order (recently closed issues on top)

Description

It seems that when using an Ios Device (Iphone) and adding Toucan to the homescreen a user needs to login every time he clicks on the Icon.

Explanation

This relates to session handling which by default is set to session length. Checking the Remember me box during login should set this to 2 weeks.

Solution

I'd need some help from an Iphone user (@LauraPirgie) to confirm this.
Please login using the checkbox and see if things work for you?

Issue reated notifications currently work via model signals.
I want this to be made more explicit at the view level. And through the use of channels.

Make invitation based

A Need/Issue should only have a single Type assigned.

When creating a new issue we should initialize the map with a marker placed at the current location of the client.

Our layout breaks on Safari 8.
@thammerl Is flexbox the only problem with Safari 8? Or did you notice further problems.
Any reason Isabella can not update? There is no version of OSX that I know of where Safari 8 is the latest available version.
We are using autoprefixer and I have added more configuration for it in 0dd072e.
But I don't think this is actually going to work, because the css looks rather similar to before.

Accommodation
non-food item
food item
legal advice

We are sending text mails for various events. One of those is the invitation of a user to an organisation.
The first screenshot shows the gmail webinterface correctly formatting the link, the second one does not.
Somebody should do some research why that is the case.

Currently we use "notification filter" and "notification rule" to refer to the same thing. We should use a consistent wording. Isabella and I decided to use "notification rule" for now.

The map currently causes a javascript error when no issues exist yet. If only one issue exists, the map does not display anything because invalid map bounds are calculated.

It’s too big and imprecise.

We should remove the "---------" option from the radio control and preselect the first issue type.

we need a better name

Marketing text etc.

When there are enough comments so that the div-scrollbar is displayed, the div scrolls to the top when the users enters an @ sign.

For example, currently reproducable with https://b2it.brickwall.at/issue/11.