Closed (fixed)
Project:
Drupal PM (Project Management)
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
4 Oct 2013 at 06:50 UTC
Updated:
17 Dec 2015 at 00:54 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
juliangb commentedSounds like a great idea.
Comment #2
d34dman commentedGood Ux improvement :)
Please note that content might be hidden too.
Lemme see what all messages need to be displayed and in which scenario.
For user/1 which has all the permisison, it could be...
No {{Project/Task/Ticket}} to display. Do you want to create a {{Project/Task/Ticket}}?
For other users, it could be much more complicated message.
Reason:
1. We got to tell them it could be because no Project/Task/Ticket have been create to which they have access to.
2. We need to check if the current user has permission to create a Project/Task/Ticket and then provide them link for creating the ticket.
3. In case #2 is negative, then we need to inform them that you would have to wait for somebody to create a Project/Task/Ticket for you.
Thoughts?
---------------------
EDIT NOTE: i had used < instead of {{ which caused the editer to conk up and hide few words.
Comment #3
purencool commentedI did not think about the permissions issue but you are right. My idea is exactly what you were alluding too. When you install the pm modules you go to the /pm and then you have to search the system to go further. I think it could be solve by adding context through text. I have add some ideas I have are below what do you think?
User/1
path: pm/organizations
comment: Please create an (this is a link)->initial organisation <-(this is a link) .
path: pm/people
comment: Please create (this is a link)-> initial people <-(this is a link) .
path: pm/teams
comment: Please create an (this is a link)-> initial team <-(this is a link).
path: pm/projects
comment: Please create an (this is a link)-> initial project <-(this is a link) Project management needs an (this is a link)-> organisation <-(this is a link) to create projects.
path: pm/tasks
comment: Please create an initial (this is a link)-> task <-(this is a link). Project management needs a (this is a link)-> project <-(this is a link) and (this is a link)-> organisation <-(this is a link) to create tasks.
path: pm/tickets
comment: Please create an initial (this is a link)-> ticket <-(this is a link). Project management needs an (this is a link)-> organisation <-(this is a link) to create tickets.
path: pm/timetrackings
comment: Not sure.
path: pm/invoices
comment: Not sure.
path: pm/expenses
comment: Not sure.
For logged in users I am not sure I would have to think about it. But D34dMan 3. is a good start.
Comment #4
juliangb commentedI think the link to add content could be useful even after there are items in the list.
How about a link to add content that is always present in the header (when permissions allow), and a useful message about no items being available being a simple (standard) plain text field?
That could be a simpler solution.
Comment #5
purencool commented@ juliangb
When you say header are you talking about the view header or the page header. But either way adding the link to would be a good idea as long as it is contextual.
Comment #6
juliangb commentedRenaming for clarity.
Comment #7
jbeuckm commentedThis as a "Global: PHP" header will create the link with a plus sign icon for adding tasks:
Comment #8
juliangb commentedThis requires using the PHP Input format on the website, which is really not recommended as if not properly configured can cause security issues on your website.
However, we could probably use similar code, but in a declared hook. That way all the PHP is still strictly in code.
Comment #9
juliangb commentedThis would be a good ux improvement.
Comment #10
nancydruI just used a "Global Text" field in the header. No PHP needed unless you want translation.
Comment #11
juliangb commentedI'm working on this.
Comment #15
juliangb commentedReady for review in branch feature-2104553.
Target for merge is develop.
These commits add a new views handler to add a consistent link onto any content view (so it is possible to use this feature with custom content types too). The link will respect pm icon settings and also redirect back to the view after node save to help a users workflow (configurable).
Comment #16
juliangb commentedMerged to develop.