amschaal / glims

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

More space for Issues on Home screen

jfass opened this issue · comments

See attached screenshot - I'm trying to use the Home screen to list and check off open Issues for all my projects. One problem is that the lab name isn't shown, so I've changed all my project names to include the PI, but having a "Lab" column would be an easier way to fix that. Another problem is that the Issue text is normally clipped, and you have to click "more" to see all of it. Could we have more room for the Issue column, or a way to increase that column size?

Alternately, I'd love a better way to have and view check lists (better than may solution in the screenshot). Maybe if the Issue column didn't clip, but wrapped? Or an option to wrap it (because you could have a lot of text in an issue, which you might not want on the Home screen)? Then I could list checkable items on separate lines, and see them all in the Home screen. I could have used separate issues for each checkable item, but that seemed tedious to view. Just food for thought ...

(Not sure why Joe opened and then immediately closed this issue, but Monica's 2cents...)

I haven't liked including the PI/Lab in the project name because:

  1. It makes the project name longer
  2. It is redundant, since there is also a Lab field that can be shown on the Projects page (or, yes, hidden)
  3. It is also redundant in the /share/biocore/projects/PI_*/ directory.

That said, I HAVE been including PI name when there's also a researcher involved (e.g., PI-postdoc_project_name)

I would prefer that the name of a project be consistent between BioBin and the server (and PPMS, but that's probably too much to hope for), and ALSO, eventually, the DNA Tech Core submission/tracking system.

This is mostly my wish-list, but something we should consider going forward...

commented

Closing this issue. Lab names are now shown, and issues show 100 characters max instead of 50 before having to click "more".

Regarding checklists, this is potentially a new plugin which should be it's own issue. If you'd like to make it an issue, you may reference this issue when doing so.