Riter release v0.10.1 - Agile Blog - Riter

Riter release v0.10.1

Meet the upgraded version of Riter which provides greater functionality, improved interface and more useful optimizations for our users. With each release we try to develop in different directions to take into account the expectations of both developers and managers. This time Riter will please you with the higher project management capacity, increased statistics awareness, rich GraphQL API and much more.

Topics management

In the new version we have significantly enriched Riter project management capabilities, so that you are able not only to create topics as it used to be, but also to modify, merge and archive them. All these actions become available on the settings page which can now be found in the main developers menu. You will see a full list of a current project topics there. Each topic has a name, a state (active or archived) and a set of possible aliases.

Topics manager

Topics states allow to divide all of them into two groups. The first one is actively used throughout the project to distinguish related stories and simplify filtering and navigation among them. The second one is intended for archived topics which are not mentioned in any project story and are not going to be in the near future. Topic archiving allows to hide it on a project story page. Note, that archived topics will still be shown in a drop-down list of hints while inputting a new topic there. If you choose it from the list, the corresponding topic will be added to the opened story and set active again. When you create a new topic, it is active by default.

The topics manager allows you to manipulate with sets of related topics. It could be bewildering to use different names for the similar topics within a project. However, it may be rather difficult to control that for big development teams. Riter prevents such ambiguities due to topics aliases which let you specify sets of synonymous values and replace them throughout all your stories with a single name. When someone tries to add an alias topic to a story, it will be substituted with the main topic name. Related topics can be merged on a settings page by specifying their names in the appropriate fields. As a result, the similar topics will be replaced with the only value in all stories where they are mentioned. If merged topics have different states, Riter sets both values to active. More project settings options will be available on the page soon.

Topics aliases

My statistics

Project statistics page includes a report on the whole team work on a particular project. This can be useful to stay aware of other developers' activities and track the current progress on the project. But in order to control your own results, it will be much more convenient to use Riter's new page - "My statistics", which you can open through your profile menu. It contains information about gross worked hours grouped by weekdays, sprints and projects that you are assigned to. Click on a specific table value to get additional data on stories which you spent this time on. You can get certain statistics using filters by projects on the right.

My statistics

GraphQL API

We are ready to delight you with the appearance of Riter's API. It is based on GraphQL standard and provides great opportunities for managing the application. In the documentation you will find a description of all available data structures, queries, mutations and requirements you should follow to use the API.

Interface and other optimizations

You will also soon see that Riter's interface and productivity have significantly changed since the last update: more responsive page elements, attractive design and higher performance. In particular, we modified the view of users' assignment on a story page. Nicknames won't be displayed near developers' avatars anymore, instead, they will be shown as tooltips.

Assignees

We have also changed a view of sprint sections on the main page. From now on, empty periods won't gather in infinite empty lists in the hope that someday you will deign to add tasks there. Now you will only see the sprints that are actually necessary and the only empty sprint for the nearest free period. Of course, "Unscheduled" section can still be used for all stories which are not scheduled yet.

Riter development team