What button text is appropriate in nuanced situation to dictate the expected behavior of clicking the button?
The End-User of our product has several peers, and they collectively work according to a ticketing system.
A ticket gets submitted and goes a group pool of tickets, a shared queue.
End-user also has their own pool of assigned tickets, their individual queue.
The queues are (essentially) a table of data with each row containing one ticket
The shared queue and individual queues look nearly identical, down to the button on each ticket's row that says "view."
On the shared queue, the 'view' button displays the ticket data, but in a "read-only" format.
On the individual queue, the 'view' button displays the ticket data in an editable format. The user can act on it, or 'perform write operations.'
An individual can't work on/advance/edit/complete a ticket that is in the shared queue.
The tickets can only be worked if they've already been moved to an individuals queue. Sometimes the End Users get busy and forget what queue they're on, and clicking the 'view' button is frustrating to them because they expect to be able to work on it, but are faced with a 'read-only' view of the ticket.
Question:
What would be the ideal text change for each button to clearly indicate what the end user will see/experience when they click it?
I'm getting a lot of pushback from technical support, devs and product management. Each feels strongly about which should say 'view' and what word/label can be used instead of 'view.' Should it be an action word like "work ticket" or "complete" or "edit" or should it be something like "preview" or something else entirely?