A feature we are thinking about, "sessions". This is just a concept, but I was thinking it might be nice to have the possibility to create a session for a certain "thing" like:
a test of a feature in a piece of software,
a how-to
a help-desk call
While capturing when a session is active, all captures are stored (chronological order) by time-stamp and all other information available. These a presented in a list, and one can select an capture for details. e.g. to edit it, delete it or export it. The complete session can be exported, e.g. all into JIRA (this application), Email or a Word-Document (FEATURE-738).
This will also be part of a "bigger" concept, the Greenshot history. Where we will store all captures in a local database where they can be retrieved. (The logic for a session is nothing more than tagging every capture with the id of the session, so they can be grouped). This should be an "opt-in" feature, or at least be clear, as a lot of people just want a simple screenshot application.
A feature we are thinking about, "sessions". This is just a concept, but I was thinking it might be nice to have the possibility to create a session for a certain "thing" like:
a test of a feature in a piece of software,
a how-to
a help-desk call
While capturing when a session is active, all captures are stored (chronological order) by time-stamp and all other information available. These a presented in a list, and one can select an capture for details. e.g. to edit it, delete it or export it. The complete session can be exported, e.g. all into JIRA (this application), Email or a Word-Document (FEATURE-738).
This will also be part of a "bigger" concept, the Greenshot history. Where we will store all captures in a local database where they can be retrieved. (The logic for a session is nothing more than tagging every capture with the id of the session, so they can be grouped). This should be an "opt-in" feature, or at least be clear, as a lot of people just want a simple screenshot application.