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

Add detailed description of what "inactive" means for the different objects #704

Closed
7 tasks done
YetAnotherGerrit opened this issue Nov 9, 2024 · 2 comments · Fixed by #718 or #719
Closed
7 tasks done

Comments

@YetAnotherGerrit
Copy link
Contributor

YetAnotherGerrit commented Nov 9, 2024

We offer on a lot of objects and object types to toggle between "active" and "inactive". It is not always intuitive what the consequences are, if you set something to inactive. We should add that.

  • Users: there are some information, but incomplete. e.g. Users are not able to login if inactive.
  • Groups: there are some information, but incomplete. e.g. Customers can see tickets in inactive groups.
  • Roles: missing
  • Organizations: seems fine
  • Overviews: missing
  • Text modules: missing
  • Macros: seems fine
  • Templates: missing
  • Checklist templates: missing
  • Trigger: missing
  • Webhook: seems fine
  • Scheduler: vague
  • Report profiles: missing
  • Time accounting activity types: missing, e.g. can it still be selected by agents? what about time that has already been booked? is it visible in reports and the ui?
  • Email accounts: review needed. Is there more?
  • Email filters: missing
  • Signatures: missing, e.g. what happens to groups that have a inactive signature set
  • Object attributes: missing
  • Core workflows: missing

Either on a central site or on their according documentation sites.

Edit RSC:

Relevant places to add a description:

Tasks

For the other features it should be clear what it means when something is disabled.

@ralf401
Copy link
Contributor

ralf401 commented Nov 11, 2024

Hi @YetAnotherGerrit, thanks for your investigation. For sure, this makes sense for some places (e.g.users, groups), but for others I don't see a benefit for the reader because it should be pretty clear (e.g. trigger). This would just bloat up the documentation.

What do you think about just adding the "unclear" items?

@YetAnotherGerrit
Copy link
Contributor Author

What do you think about just adding the "unclear" items?

Yeah, that makes sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment