There should be a single scrolling on the screen.

• First elements - unreadnotifications
• Other elements - allnotifications

They shouldn't be separated

Rework automatic release: add tagging and release versions instead of just one release build

So now there should be

• [x] a tag for each push on main (for each version)
• [x] version autogeneration
• [x] a release with that version and all the compiled files of the application (executables)

Added linting rule for the styleguide's rule on naming unused parameters in callback functions

This linting rule ensures that no one programmer in our team under our Styleguide.md guidelines can ever write callback functions in dart so that there is one unused parameter that is not named like '_'*n, n>0.

This rule comes from the Effective Dart guideline which is what our guidelines inherit from.

The Effective Dart guideline does not have a lint for this rule by default, so we coded it ourselves to ensure the quality of complying with the rule.

As for now, user can not freeze a queue if it's in to-do list, i.e. user is on duty for this queue. This button is hidden. However, it might confuse user and he would not know how to freeze a queue.

So, let's show this button all the time. However, if the user is on duty and he taps on the "freeze" button, then show a pop-up alert window saying "You can't freeze this queue since you are on duty. Please complete or skip this queue to be able to freeze it". Below this message add two buttons

• "Skip and freeze" - if a user taps on this button, then app will send two requests: POST /tasks/skip and then POST /queues/freeze/{queueId}
• "Close" - then user will just close this alert. Nothing will change.

Description with up to date info in Swagger: https://innoqueue-dev.herokuapp.com/swagger-ui/index.html#/User

Change 1

Before:

POST /user/signup Request body:

{
  "user_name": "string",
  "fcm_token": "string"
}

Response

{
  "token": "string",
  "user_id": 0
}

After:

** POST** /user/signup Request body:

{
  "userName": "string",
  "fcmToken": "string"
}

Response

{
  "token": "string",
  "userId": 0
}

Change 2

Before:

GET /settings Response

{
  "completed": true,
  "skipped": true,
  "freeze": true,
  "name": "string",
  "joined_queue": true,
  "left_queue": true,
  "your_turn": true
}

After:

GET /user Response

{
  "userName": "string",
  "completed": true,
  "skipped": true,
  "joinedQueue": true,
  "freeze": true,
  "leftQueue": true,
  "yourTurn": true
}

Change 3

Before:

PATCH /settings Request body:

{
  "name": "string",
  "completed": true,
  "skipped": true,
  "joined_queue": true,
  "freeze": true,
  "left_queue": true,
  "your_turn": true
}

Response

{
  "completed": true,
  "skipped": true,
  "freeze": true,
  "name": "string",
  "joined_queue": true,
  "left_queue": true,
  "your_turn": true
}

After:

PATCH /user Request body:

{
  "userName": "string",
  "completed": true,
  "skipped": true,
  "joinedQueue": true,
  "freeze": true,
  "leftQueue": true,
  "yourTurn": true
}

Response

{
  "userName": "string",
  "completed": true,
  "skipped": true,
  "joinedQueue": true,
  "freeze": true,
  "leftQueue": true,
  "yourTurn": true
}

After this backend implementation https://github.com/InnoQueue/Backend/issues/150 Backend won't return hash_code field in JSON response. So, mobile app should also remove it and do not use hash_code anyhow.

Should be implemented after: https://github.com/InnoQueue/Backend/issues/150

Each URL should start with prefix /api/v1/. For example, before: GET https://innoqueue.herokuapp.com/queues after: GET https://innoqueue.herokuapp.com/api/v1/queues

So, add this prefix to ALL requests

Should be implemented after this: https://github.com/InnoQueue/Backend/issues/149

In "To-Do" tab show tasks for which the user will be assigned as a next user. Show these tasks below the main list. See ref:

Should be completed after https://github.com/InnoQueue/Backend/issues/128

In "Queues" section add a button to the top right corner with name sort. There should be the following options to select:

• queue name
• participant name
• date joined
• upcoming to-dos

The selected option should be saved in app cache. So, next time when the app is launched the queues order preserves the same sorting option.

Should be implemented after: https://github.com/InnoQueue/Backend/issues/91