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

ipdevinfo maintenance task link should be to task details view, not the task editor #2255

Closed
ingeborgoh opened this issue Feb 2, 2021 · 2 comments
Assignees
Milestone

Comments

@ingeborgoh
Copy link
Contributor

Nav 5.1.2

The intuitive way to cancel a Maintenance task is to search for the netbox and click on the "active maintenance" task in the right column in ip device info.

Then you end up in /nav.../maintenance/edit/nnnn/

You can then edit, but not cancel.

The way that works is to visit the maintenance calendar, scroll through the rainbow, find the task. You then end up in /nav.../maintenance/view/nnnn/ and can cancel.

We would like a "Cancel now" button on the edit page (or an "Edit" button on the .../view/ page) and that you end up on the same page from both calendar view and ip device info.

@lunkwill42
Copy link
Member

IMHO, the problem here is that ipdevinfo links to the task editor, rather than the task view. For me, it's not intuitive that clicking the task description should do anything but display more details about the task. The user clicking the link might not even have access to edit the task, even if they should have access to view the task details.

My counter-suggestion would therefore be that the link goes to /maintenance/view/nnn/ instead.

@ingeborgoh
Copy link
Contributor Author

I agree. No direct Edit from ipdevinfo. And you end up the same place regardless of which route you choose to look for the maintenance task.

@lunkwill42 lunkwill42 changed the title Make it easier to cancel maintenance task ipdevinfo maintenance task link should be to task details view, not the task editor Mar 17, 2021
@lunkwill42 lunkwill42 added this to the 5.1.3 milestone Mar 17, 2021
@lunkwill42 lunkwill42 self-assigned this Mar 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants