Hi, I’m the engineer who worked on the UI of this ticket form. I’ve been looking into this issue and want to make sure I fully understand the expected behavior. When pressing Enter in the ticket fields, I’m not sure if the behavior I’m seeing matches what you’re experiencing.
Could you clarify a bit?
Which field are you typing in when the unexpected submission happens?
Should pressing Enter never submit the ticket, or only not submit in certain fields?
Once I have a bit more detail, I can continue to look into this request.
I believe I was filling out the "Owner" field when I pressed the “enter” key to confirm the selection and it submitted the ticket, very annoying since it was a bulk ticket creation. I feel that the ticket should never be submitted until you click "Save".
If we're on the subject of ticket UI. I noticed the ticket form does not expand to the page size, it's size is relative to the ticket list table causing us to have to scroll through the ticket form. I personally enjoy the old UI, not sure why but it feels more intuitive. Perhaps is the way things are spaced and sized.
As well, when editing a ticket with the new UI, it is not intuitive. For changing things, such as status, it almost feels like I stumble onto the way to edit the fields as it looks like it is only displaying the ticket info and there is no clear indicator that you can make edits. There is nothing to confirm the changes are made, so Im left looking for a save button and worried if the changes are going to stick.
When using the bulk edit tool to open tickets on the miner list page, it is inconvenient that it redirects you to a new page instead of opening a new tab.
And then… There's no way to get the the miner details page from the ticket page, so we would need to search for the miner using its, SN, MAC, or Device Name.
When searching through tickets, there is no easy way to enter a list of miners who's tickets we would like to bulk edit. Having the ability to enter a list of Miner Ids or MACs would make bulk editing tickets much quicker by magnitudes.
Thanks for the prompt feedback and additional context. From a UX perspective, we followed what is largely the industry standard behavior. For example, if you create a new Jira ticket a modal opens up. If you hit "enter" while your cursor is in a one-line form field, it submits the ticket. Doesn't mean it has to be this way but let's see how the rest of the community feels.
Comments
3 comments
Hi, I’m the engineer who worked on the UI of this ticket form. I’ve been looking into this issue and want to make sure I fully understand the expected behavior. When pressing Enter in the ticket fields, I’m not sure if the behavior I’m seeing matches what you’re experiencing.
Could you clarify a bit?
Once I have a bit more detail, I can continue to look into this request.
Thanks!
I believe I was filling out the "Owner" field when I pressed the “enter” key to confirm the selection and it submitted the ticket, very annoying since it was a bulk ticket creation. I feel that the ticket should never be submitted until you click "Save".
If we're on the subject of ticket UI. I noticed the ticket form does not expand to the page size, it's size is relative to the ticket list table causing us to have to scroll through the ticket form. I personally enjoy the old UI, not sure why but it feels more intuitive. Perhaps is the way things are spaced and sized.
As well, when editing a ticket with the new UI, it is not intuitive. For changing things, such as status, it almost feels like I stumble onto the way to edit the fields as it looks like it is only displaying the ticket info and there is no clear indicator that you can make edits. There is nothing to confirm the changes are made, so Im left looking for a save button and worried if the changes are going to stick.
When using the bulk edit tool to open tickets on the miner list page, it is inconvenient that it redirects you to a new page instead of opening a new tab.
And then… There's no way to get the the miner details page from the ticket page, so we would need to search for the miner using its, SN, MAC, or Device Name.
When searching through tickets, there is no easy way to enter a list of miners who's tickets we would like to bulk edit. Having the ability to enter a list of Miner Ids or MACs would make bulk editing tickets much quicker by magnitudes.
Thanks for the prompt feedback and additional context. From a UX perspective, we followed what is largely the industry standard behavior. For example, if you create a new Jira ticket a modal opens up. If you hit "enter" while your cursor is in a one-line form field, it submits the ticket. Doesn't mean it has to be this way but let's see how the rest of the community feels.
Please sign in to leave a comment.