Custom Query (2152 matches)
Results (1030 - 1032 of 2152)
Ticket | Resolution | Summary | Owner | Reporter | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
#190 | fixed | Package comments | pudo | dread | |||||||||||||||
Description |
Cost 7 days When viewing a package, users can read user comments and leave their own. Users need to be logged in to leave a message. Comments appear immediately. A mechanism for deleting unwanted comments is provided to an authorized user. Comments are sorted with the most recent first. Comments are available for read, creation and deletion in both the Web UI and over the REST API. The admin for the package and a superuser can delete unwanted comments, both on the package page and a collation of all comments on their user page. Users can delete their own comments(?) Need to consider whether over the REST API we encourage the use of a 'frontend user' APIKEY which can be used to leave comments for another, actual user. Example at bottom of package page: Leave a comment:
Comments:
Implementation details:Comments table is with columns:
|
||||||||||||||||||
#902 | fixed | Package buttons not clickable / Improve submenu tabs | rgrp | dread | |||||||||||||||
Description |
On a package page there are three buttons to the right - View, Edit, History. Each of these buttons contain an icon and the text, but you can only activate the button by clicking on the icon. When you click on the part of the button where the text is (about 50% of the button) then nothing happens. Using: Chrome, Firefox |
||||||||||||||||||
#691 | duplicate | Package Relationships | thejimmyg | johnbywater |