You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, closing a rack request ticket automatically creates an device record with an ID assigned in the OpenDCIM MySQL database. It would be ideal to have an option to close one or more tickets simply with one click, by assigning only a closing date in the MySQL database. This would provide more flexibility for users who use bulk imports or create equipment via the API.
for example on the home page, the rack request table has a column with a checkbox for multiple selection and outside the table a button "close the ticket(s)" and a date selector for "closing date"
This allows users who use import new devices or create new devices with API this facilitates the workflow
The ideal would be to add ticket creation with API
For organizations that already use ticketing solutions, this can lead to duplicates or additional complexity to manage. The OpenDCIM API does not have a ticket section at the moment. This would have allowed to automate ticket creation on OpenDCIM from another ticketing solution.
++ an option allowing actions on the racks (installation, move, deletion, labeling)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
Currently, closing a rack request ticket automatically creates an device record with an ID assigned in the OpenDCIM MySQL database. It would be ideal to have an option to close one or more tickets simply with one click, by assigning only a closing date in the MySQL database. This would provide more flexibility for users who use bulk imports or create equipment via the API.
for example on the home page, the rack request table has a column with a checkbox for multiple selection and outside the table a button "close the ticket(s)" and a date selector for "closing date"
This allows users who use import new devices or create new devices with API this facilitates the workflow
The ideal would be to add ticket creation with API
For organizations that already use ticketing solutions, this can lead to duplicates or additional complexity to manage. The OpenDCIM API does not have a ticket section at the moment. This would have allowed to automate ticket creation on OpenDCIM from another ticketing solution.
++ an option allowing actions on the racks (installation, move, deletion, labeling)
thx,
Alex.
Beta Was this translation helpful? Give feedback.
All reactions