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

Ticket Object Manager Greyed Out - Not Editable #1525

Open
tdavison1 opened this issue Oct 11, 2017 · 6 comments
Open

Ticket Object Manager Greyed Out - Not Editable #1525

tdavison1 opened this issue Oct 11, 2017 · 6 comments

Comments

@tdavison1
Copy link

Infos:

  • Used Zammad version: 2.0.x
  • Used Zammad installation source: CentOS via RPM
  • Operating system: CentOS 7 (all patches)
  • Browser + version: Mac High Siera & Windows 7 Firefox 56.0

Expected behavior:

  • Ability to edit the objects (eg; Group) to set them as required when filling out a ticket.

Actual behavior:

  • The objects are not editable. I can however edit any objects that I have created, just not those created by a default install. I have tried this as a LDAP user and also full default admin user. The only editable item is Type - all the others are in the class="is-grayed-out u-notAllowed"
    image

Steps to reproduce the behavior:

@tdavison1
Copy link
Author

Just tried another install on blank Centos 7 and Ubuntu with the same results.

@hanneshal
Copy link
Contributor

Thats correct and the desired behaviour. Zammad needs some basics to rely on, these fields are part of this.
Which of those attributes do you want to edit ?

@hanneshal hanneshal self-assigned this Oct 17, 2017
@tdavison1
Copy link
Author

Hi,

We absolutely want to keep these fields, we just want to be able to change the screens to make them mandatory fields for example;
image

By default they are not shown or mandatory. Is this something that is possible?

Thanks

@tdavison1
Copy link
Author

I have upgraded to V2.1 release with the same results.

Is there another way to make these fields shown on the ticket forms?

Thanks

@tbsfnk
Copy link

tbsfnk commented Nov 9, 2020

Any news on this?

@zammad zammad locked and limited conversation to collaborators Nov 9, 2020
@MrGeneration
Copy link
Member

Sorry but I'm locking the conversation to contributors only.
Please don't ping/bump issues on this repository as it creates a lot of noise.

We will update issues accordingly as soon as anything moves.
This issue is a feature backlog and has no roadmap yet.

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

No branches or pull requests

6 participants