Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature request] Support more partiticaption status like needs-action #2135

Open
Thaodan opened this issue Oct 18, 2022 · 1 comment
Open

Comments

@Thaodan
Copy link

Thaodan commented Oct 18, 2022

Expected behaviour

Nextcloud tasks should support more participation statuses such as needs action or delegated (#72).
The UI should show something like Status: <Status>

The usage of such an extended status view would be to be able to visualize the status of a task better.
This includes things such as: blocked by another task, waiting and so on.

Actual behaviour

The only supported state right now is the done or undone state portrait by the checkbox next to the taskname.

Server configuration

Nextcloud version: 24.0.4

Tasks version: 0.14.4-2

List of activated apps:

Not relevant

Nextcloud configuration:
Not relevant

See also:

@raimund-schluessler
Copy link
Member

The app already has the possibility to set the status of a task in the right sidebar:
grafik

We offer the following choices for the status:

const statusOptions = [
{
displayName: t('tasks', 'Needs action'),
type: 'NEEDS-ACTION',
icon: 'IconAlertBoxOutline',
optionClass: 'active',
},
{
displayName: t('tasks', 'Completed'),
type: 'COMPLETED',
icon: 'IconCheck',
optionClass: 'active',
},
{
displayName: t('tasks', 'In process'),
type: 'IN-PROCESS',
icon: 'IconTrendingUp',
optionClass: 'active',
},
{
displayName: t('tasks', 'Canceled'),
type: 'CANCELLED',
icon: 'IconCancel',
optionClass: 'active',
},
]
according to RFC 5545, section 3.8.1.11 https://datatracker.ietf.org/doc/html/rfc5545#section-3.8.1.11

In order to support the Participation status according to https://datatracker.ietf.org/doc/html/rfc5545#section-3.2.12 as you propose, we would first need to implement attendees. Without the option to set or invite attendees, it does not make sense to implement a participation status.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants