Real-time Agile board

Feature description

From Agile 1.6.7, a new feature was added - Added async board update. In other words, it is a real-time Agile board. If you change something on it, then it is automatically and visibly applied for anyone else.

We will show you an example for one logged user in Redmine doing changes and other anonymous (i.e. not logged in Redmine at all) will see the changes instantly.

Please see the below screenshot reference. On the left, we use have a Mozilla Firefox browser with admin logged-in user. On the right, we have anonymous user (not logged-in) that has opened the same Agile board, the browser here is Google chrome. And we move this ticket "Swimlanes" as admin user.

two_boards.png

As a result, it is now in the "in progress" column in the anonymous user board too at the same time when we just dropped the ticket.

moved.png

How to enable/disable the feature?

To switch on or off this functionality, please go to Administration (on top) - Agile - General tab. And here, scroll down to the bottom and check or uncheck the last option that says Real-time agile boards. Please see this picture to make the situation clear.

real_time_button_agile.png

Passenger settings

There is a reconnection when connection is lost and work taking into account cable.yml. Now: 1. If the plugin is installed and config/cable.yml is not added - the async adapter works 2. If the plugin is installed and cable.yml is added - the adapter specified in cable.yml is activated (attention: for some adapters, you may need to add a gem to the Gemfile - there will be errors in the console about this).

Example config/cable.yml:

development:
  adapter: async

test:
  adapter: test

production:
  adapter: redis

Passenger: This application server requires the mandatory use of the redis adapter for normal operation (activated via config/cable.yml and adding the location block to the server section for Redmine and restarting the server via stop+start

  location ~* rup_cable {
    passenger_force_max_concurrent_requests_per_process 0;
  }

Important: without it the server will fail.

Video demonstration

Was this article helpful? Yes  No
281 from 281 found this helpful