Bug 716336 - RFE: view of problem reports from a system's history
Summary: RFE: view of problem reports from a system's history
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: 0.6
Hardware: Unspecified
OS: Unspecified
low
low vote
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact:
URL:
Whiteboard: UX
Depends On: 715243
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-24 02:56 UTC by Dan Callaghan
Modified: 2020-06-02 11:59 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 715243
Environment:
Last Closed: 2020-06-02 11:59:45 UTC


Attachments (Terms of Use)

Description Dan Callaghan 2011-06-24 02:56:58 UTC
+++ This bug was initially created as a clone of Bug #715243 +++

--- Additional comment from kvolny on 2011-06-23 19:59:48 EST ---

now I have noticed (um, blind me, sorry) that the report appears in system history, but ...

a) the text is incomplete
b) it is not linkable

- could this be resolved as well (like a link "problems history" next to "report problem")?

Comment 3 Tomas Klohna 🔧 2019-04-12 14:46:02 UTC
The new_value field that is under Activity is limited to only 60 chars. Patch for this needs to go to develop branch. Might be better idea to consider if we shouldn't just a create a separate tab with "Reported Problems" that would list all reported problems with the ability to link to them (as that is currently not possible on the System's Activity page). Or we can leave the new_value as it is and add only the new page.

Comment 4 Martin Styk 2020-06-02 11:59:45 UTC
Hello,

thank you for opening issue in Beaker project.
This issue was marked with component "web ui".
As we are not planning to address any further issues in current UI, due to technical stack and not being able to work with Python 3 codebase, I'm closing this issue as WONTFIX.
New UI will be reimplemented within new versions of Beaker.

If you have any questions feel free to reach out to me.

Best regards,
Martin <martin.styk>


Note You need to log in before you can comment on or make changes to this bug.