Re: [Apache Bloodhound] #21: Site notification of ticket and wiki activity
#21: Site notification of ticket and wiki activity
+--
Reporter: gjm| Owner: gjm
Type: task | Status: accepted
Priority: blocker| Milestone:
Component: siteadmin |Version:
Resolution: | Keywords:
+--
Changes (by gjm):
* status: new = accepted
Comment:
All notifications to go to bloodhound-commits@incubator.apache.org as
discussed in [http://mail-archives.apache.org/mod_mbox/incubator-
bloodhound-
dev/201203.mbox/%3CCABD8fLUHF1JnZmKXCv7nXVgCJhetiWRZDVMEMDGuX3N97_TN1w%40mail.gmail.com%3E
this email].
The following option has now been set in the site's trac.ini:
{{{
#!ini
[notification]
smtp_always_cc = bloodhound-commits@incubator.apache.org
}}}
Note that wiki edits still require need to be looked at.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/21#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #21: Site notification of ticket and wiki activity
#21: Site notification of ticket and wiki activity + Reporter: gjm| Owner: gjm Type: task | Status: closed Priority: blocker| Milestone: Component: siteadmin |Version: Resolution: fixed | Keywords: + Changes (by gjm): * status: accepted = closed * resolution: = fixed Comment: Wiki updates should now also go to bloodhound-commits@incubator.apache.org The version of TracWikiNotification has a few bugs that I noted and raised on the plugin's bitbucket issue system including https://bitbucket.org/mitar/trac-wikinotification/issue/7 which I have patched on the running copy. The [http://trac-hacks.org/intertrac/AnnouncerPlugin AnnouncerPlugin] might be a better alternative in the longer term but there are suggestions that it could break compatibility with some plugins so more investigation is required. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/21#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] Ui/Version modified
Page Ui/Version was changed by jdreimann Diff URL: https://issues.apache.org/bloodhound/wiki/Ui/Version?action=diffversion=3 Revision 3 Changes: ---8--8--8--8--8--8--8--8 Index: Ui/Version = --- Ui/Version (version: 2) +++ Ui/Version (version: 3) @@ -1,5 +1,19 @@ -Can be found here for now: -https://svn.apache.org/repos/asf/incubator/bloodhound/trunk/doc/html-templates/version.html +[https://svn.apache.org/repos/asf/incubator/bloodhound/trunk/doc/html-templates/version.html HTML mockup] - follows the basic Ui/Layout. +The Version view provides a description, which can be edited with Wiki formatting, just as a description in a Ticket can. The only difference is that the amount of text before hiding the rest behind a 'More' button. When clicked, the box simply expands in place and provides a 'Less' button. -Description to follow. +It also shows a progress bar of the number of Tickets closed vs the total number of Tickets associated with this Version. + +== Button bar == +Displays options to view Milestones, My Tickets, All Tickets, Projects and Components associated with this Product. My Tickets will be selected by default, but when a user changes the selection to (for example) Components, that selection should 'stick'. That means when the user navigates to another page with a similar button bar, such as Ui/Product or Ui/Milestone, the Components button will also be selected on them. + +=== Milestones === +Shows Milestones related to the Version in a left-bound tab style. + +How this should look specifically is still ''work in progress''. + +=== My Tickets === +Same as on the Ui/Dashboard, but filtered to only tickets related to this Version. + +=== All Tickets, Projects, Components === +Shows all tickets / Projects / Components related to the Version. ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/Ui/Version Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker This is an automated message. Someone added your email address to be notified of changes on 'Ui/Version' page. If it was not you, please report to .
Re: [Apache Bloodhound] #11: Describe Product and Version screens
#11: Describe Product and Version screens +--- Reporter: jdreimann | Owner: jdreimann Type: task | Status: new Priority: blocker| Milestone: Component: dashboard |Version: Resolution: | Keywords: +--- Comment (by jdreimann): Done, as far as they're decided up to now. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/11#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #23: quick ticket functionality should check that the ticket module is active
#23: quick ticket functionality should check that the ticket module is active +- Reporter: gjm| Owner: gjm Type: defect | Status: new Priority: major | Milestone: RC1 for initial release Component: dashboard |Version: Resolution: | Keywords: +- Changes (by olemis): * cc: olemis+bh@… (added) Comment: sorry it's not clear to me what needs to be done exactly . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/23#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #23: quick ticket should check for correct ticket module to use
#23: quick ticket should check for correct ticket module to use +- Reporter: gjm| Owner: gjm Type: defect | Status: new Priority: major | Milestone: RC1 for initial release Component: dashboard |Version: Resolution: | Keywords: +- Comment (by olemis): hmmm ... IMO what should be done is to iterate over instances of `IRequestHandler` and determine which one matches /newticket path -- Ticket URL: https://issues.apache.org/bloodhound/ticket/23#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] BloodhoundInstall modified
Page BloodhoundInstall was changed by gjm
Diff URL:
https://issues.apache.org/bloodhound/wiki/BloodhoundInstall?action=diffversion=3
Revision 3
Changes:
---8--8--8--8--8--8--8--8
Index: BloodhoundInstall
=
--- BloodhoundInstall (version: 2)
+++ BloodhoundInstall (version: 3)
@@ -53,6 +53,15 @@
{{{
sudo /etc/init.d/postgresql restart
}}}
+
+For MySQL these instructions may work on Ubuntu 11.10:
+ {{{
+ sudo apt-get install mysql-client mysql-server
+ mysql --user=root --password -e CREATE DATABASE bloodhound DEFAULT
CHARACTER SET utf8 COLLATE utf8_bin;
+ mysql --user=root --password -e GRANT ALL ON bloodhound.* TO
bloodhound@localhost IDENTIFIED BY 'asecurepasswd';
+ }}}
+
+In the form specified above, the mysql commands will request a password which
will be the password set on installing mysql. To change this password, you can
run {{{sudo dpkg-reconfigure mysql-server-5.1}}}.
== Installation Script ==
---8--8--8--8--8--8--8--8
--
Page URL: https://issues.apache.org/bloodhound/wiki/BloodhoundInstall
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
This is an automated message. Someone added your email address to be
notified of changes on 'BloodhoundInstall' page.
If it was not you, please report to .
[Apache Bloodhound] BloodhoundInstall modified
Page BloodhoundInstall was changed by gjm
Diff URL:
https://issues.apache.org/bloodhound/wiki/BloodhoundInstall?action=diffversion=4
Revision 4
Changes:
---8--8--8--8--8--8--8--8
Index: BloodhoundInstall
=
--- BloodhoundInstall (version: 3)
+++ BloodhoundInstall (version: 4)
@@ -14,10 +14,12 @@
At the moment it is also recommended that you install virtualenv ({{{sudo
apt-get install python-virtualenv}}} or {{{pip install virtualenv}}}) as for
systems with existing python installations, it allows you to install packages
with lower impact to the system provided installation. In addition, virtualenv
is a requirement if you wish to take advantage of the installer script.
== Databases ==
-Apache Bloodhound also requires a database and it supports the following
popular databases out of the box: [http://sqlite.org/ SQLite],
[http://www.postgresql.org/ PostgreSQL], and [http://mysql.com/ MySQL]. For the
moment this guide does not discuss installing with a MySQL database.
+Apache Bloodhound also requires a database and it supports the following
popular databases: [http://sqlite.org/ SQLite], [http://www.postgresql.org/
PostgreSQL], and [http://mysql.com/ MySQL].
+=== Easy Option: SQLite ===
Installing Apache Bloodhound with SQLite is the easiest option as Python comes
with SQLite integrated into it. In addition, there are no special access rights
required to create or interact with an SQLite database as it is stored in a
local file. For larger production installations, SQLite may not be considered
appropriate and lacks the possible advantage of using a separate server for the
database.
+=== Recommended Option: PostgreSQL ===
Installing with PostgreSQL is complicated by having to create users and a
database on the server and adjusting permissions to allow access. It also adds
the following dependencies:
* [http://www.postgresql.org/ PostgreSQL]
* [http://initd.org/psycopg/ psycopg2]
@@ -54,7 +56,10 @@
sudo /etc/init.d/postgresql restart
}}}
-For MySQL these instructions may work on Ubuntu 11.10:
+=== If MySQL is your only choice ===
+Note that the Installation Script does not yet allow for installing with a
MySQL database.
+
+Although MySQL is supported by Bloodhound, the likelihood of success may be
expected to be dependent on the version of MySQL you are trying to use. The
MySQL 5.0.x versions are recommended at this point but as this is investigated,
further this page will be updated. For MySQL these instructions may work on
Ubuntu 11.10 (currently using MySQL 5.1.61):
{{{
sudo apt-get install mysql-client mysql-server
mysql --user=root --password -e CREATE DATABASE bloodhound DEFAULT
CHARACTER SET utf8 COLLATE utf8_bin;
@@ -62,6 +67,8 @@
}}}
In the form specified above, the mysql commands will request a password which
will be the password set on installing mysql. To change this password, you can
run {{{sudo dpkg-reconfigure mysql-server-5.1}}}.
+
+To continue the installation, refer to BloodhoundDetailedInstallation before
continuing to the Testing the Server section below.
== Installation Script ==
---8--8--8--8--8--8--8--8
--
Page URL: https://issues.apache.org/bloodhound/wiki/BloodhoundInstall
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
This is an automated message. Someone added your email address to be
notified of changes on 'BloodhoundInstall' page.
If it was not you, please report to .
[Apache Bloodhound] Ui/Milestone added
Page Ui/Milestone was added by jdreimann Content: ---8--8--8--8--8--8--8--8 [https://svn.apache.org/repos/asf/incubator/bloodhound/trunk/doc/html-templates/milestone.html HTML mockup]. Follows the basic Ui/Layout. ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/Ui/Milestone Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker This is an automated message. Someone added your email address to be notified of changes on 'Ui/Milestone' page. If it was not you, please report to .
[Apache Bloodhound] #33: In place adding of versions/milestones and view more in layout
#33: In place adding of versions/milestones and view more in layout ---+ Reporter: jdreimann | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: ui design |Version: Keywords: | ---+ As introduced in the [http://mail-archives.apache.org/mod_mbox/incubator- bloodhound-dev/201204.mbox/%3CCAKoya92nY%2BDkW-FAq-SDhZbTo- 42Be6DogVt5oLLDqk68djRFw%40mail.gmail.com%3E mailing list discussion] and [http://mail-archives.apache.org/mod_mbox/incubator-bloodhound- dev/201204.mbox/%3C4F8847E6.6090605%40wandisco.com%3E Gary's suggestion]. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/33 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #34: Fix button alignment on Wiki, Report, Ticket and other pages
#34: Fix button alignment on Wiki, Report, Ticket and other pages ---+- Reporter: jdreimann | Owner: nobody Type: defect | Status: new Priority: major | Milestone: RC1 for initial release Component: ui design |Version: Keywords: | ---+- Currently the buttons are always verticall stacked, while they should really be horizontally stacked. This will be a styling issue of sorts. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/34 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #39: Disable old Trac CSS files
#39: Disable old Trac CSS files
+-
Reporter: jdreimann | Owner: nobody
Type: task | Status: new
Priority: critical | Milestone: RC1 for initial release
Component: ui design |Version:
Resolution: | Keywords:
+-
Comment (by gjm):
If we are only removing trac provided common/css/*.css we could probably
do this using the post_process_request of an IRequestFilter in the
bloodhound theme. This way we would not have to change trac itself, which
would be good.
I believe something like this could do the job:
{{{#!python
links = req.chrome.get('links',{})
indices = [i for (i,ss) in enumerate(links.get('stylesheet',[]))
if ss.get('href').startswith(req.base_path +
'/chrome/common/css/')]
for i in indices:
del links['stylesheet'][i]
}}}
This is based on how the theme engine code does the job, though a fair bit
more condensed.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/39#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #38: Make the product name field unique
#38: Make the product name field unique ---+- Reporter: gjm | Owner: gjm Type: task | Status: closed Priority: critical | Milestone: RC1 for initial release Component: multiproduct |Version: Resolution: fixed | Keywords: ---+- Changes (by gjm): * status: accepted = closed * resolution: = fixed Comment: I think that this can be called done. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/38#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #39: Disable old Trac CSS files
#39: Disable old Trac CSS files
+-
Reporter: jdreimann | Owner: gjm
Type: task | Status: accepted
Priority: critical | Milestone: RC1 for initial release
Component: ui design |Version:
Resolution: | Keywords:
+-
Comment (by gjm):
r1329142 should fix and for a bonus looks a bit more readable to me:
{{{svn diff -r 1329141 bloodhound_theme/bhtheme/theme.py}}}:
{{{
#!diff
Index: bloodhound_theme/bhtheme/theme.py
===
--- bloodhound_theme/bhtheme/theme.py (revision 1329114)
+++ bloodhound_theme/bhtheme/theme.py (working copy)
@@ -78,14 +78,14 @@
def post_process_request(self, req, template, data, content_type):
Post process request filter.
-Removes all trac provided css if required
+Removes all trac provided css if required
if self.disable_all_trac_css:
links = req.chrome.get('links',{})
-indices = [i for (i,ss) in
enumerate(links.get('stylesheet',[]))
- if ss.get('href').startswith(req.base_path +
-
'/chrome/common/css/')]
-for i in indices:
-del links['stylesheet'][i]
+stylesheets = links.get('stylesheet',[])
+if stylesheets:
+path = req.base_path + '/chrome/common/css/'
+links['stylesheet'] = [ss for ss in stylesheets
+ if not
ss.get('href').startswith(path)]
return template, data, content_type
class QuickCreateTicketDialog(Component):
}}}
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/39#comment:8
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #23: quick ticket should check for correct ticket module to use
#23: quick ticket should check for correct ticket module to use +- Reporter: gjm| Owner: gjm Type: defect | Status: accepted Priority: major | Milestone: RC1 for initial release Component: dashboard |Version: Resolution: | Keywords: +- Changes (by gjm): * status: new = accepted Comment: OK, I think it is about time that the quick ticket functionality worked with the product system so I'll take this on now. I'll go with the relatively simple check in my last comment but I'll try to throw in changes to the html to get the product field active and conditionally show the Create Ticket button. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/23#comment:7 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #23: quick ticket should check for correct ticket module to use
#23: quick ticket should check for correct ticket module to use +- Reporter: gjm| Owner: gjm Type: defect | Status: closed Priority: major | Milestone: RC1 for initial release Component: dashboard |Version: Resolution: fixed | Keywords: +- Changes (by gjm): * status: accepted = closed * resolution: = fixed Comment: r1329220 adds a method to check for appropriate ticketmodule. Also turns off functionality if either both ticketmodule candidate classes are active or both deactivated. r1329223 shows a product field in quickticket form on condition that the product field is available. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/23#comment:8 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #13: Rename About Trac to System Information and move it to the footer
#13: Rename About Trac to System Information and move it to the footer --+- Reporter: jdreimann| Owner: gjm Type: enhancement | Status: new Priority: minor| Milestone: Component: dashboard|Version: Resolution: | Keywords: --+- Comment (by jdreimann): The pages this links to also needs to be overhauled: /about or /main/about - this currently displays only Trac branding. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/13#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #41: Wiki edit side-by-side doesn't work
#41: Wiki edit side-by-side doesn't work ---+ Reporter: jdreimann | Owner: nobody Type: defect | Status: new Priority: major | Milestone: Component: dashboard |Version: Keywords: | ---+ This is likely caused by a lack of CSS describing how the preview should be displayed (after #39 was completed). I'm not suggesting #39 should be reverse, I suggest we identify what's missing and add this to bloodhound.css -- Ticket URL: https://issues.apache.org/bloodhound/ticket/41 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #39: Disable old Trac CSS files
#39: Disable old Trac CSS files +- Reporter: jdreimann | Owner: gjm Type: task | Status: accepted Priority: critical | Milestone: RC1 for initial release Component: ui design |Version: Resolution: | Keywords: +- Comment (by olemis): afaict +1 -- Ticket URL: https://issues.apache.org/bloodhound/ticket/39#comment:12 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #23: quick ticket should check for correct ticket module to use
#23: quick ticket should check for correct ticket module to use
+-
Reporter: gjm| Owner: gjm
Type: defect | Status: reopened
Priority: major | Milestone: RC1 for initial release
Component: dashboard |Version:
Resolution: | Keywords:
+-
Comment (by gjm):
OK, I see that this is an alternative fix now as it effectively replaces
the requirement to find the right {{{TicketModule}}} with getting the
{{{TicketSystem}}}. That looks fine.
At the moment, the only other comment I would have is that is traditional
in Trac to define interface methods without the self argument. Assuming
that everyone is happy with this change, I'll just drop the {{{self}}}
from the {{{IQuickCreateTicketBackend.create}}} method.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/23#comment:12
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #42: Disable quick ticket button when user doesn't have sufficient permission
#42: Disable quick ticket button when user doesn't have sufficient permission -+- Reporter: jdreimann| Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: RC1 for initial release Component: dashboard|Version: Keywords: | -+- See summary. This button shouldn't just disappear, but rather add the class disabled, which will stop people from being able to click it. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/42 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #15: Update styling to Bootstrap
#15: Update styling to Bootstrap
+
Reporter: jdreimann | Owner: olemis
Type: task | Status: new
Priority: major | Milestone:
Component: dashboard |Version:
Resolution: | Keywords:
+
Comment (by olemis):
Updated patch for milestones admin panel and added two more for components
and versions admin panels.
My patch queue looks like this (beware of the order to apply them ''';)'''
{{{
#!sh
$ hg qapplied
t39/t39_r1328689_indexerror.diff
t23/t23_r1328689_flexible_qct.diff
t15/t15_r1328689_admin_webui.diff
t15/t15_r1328689_admin_logging.diff
t15/t15_r1328689_admin_basics.diff
t15/t15_r1328689_admin_enums.diff
t15/t15_r1328689_admin_perms.diff
t15/t15_r1328689_admin_milestones.diff
t15/t15_r1328689_admin_components.diff
t15/t15_r1328689_admin_versions.diff
}}}
Right now plugins and repository admin panels should be the only ones left
to get all admin section UI updated. Nonetheless , I'll add similar
replacements for !ThemeEnginePlugin and !IniAdminPlugin .
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/15#comment:5
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #23: quick ticket should check for correct ticket module to use
#23: quick ticket should check for correct ticket module to use
+-
Reporter: gjm| Owner: gjm
Type: defect | Status: reopened
Priority: major | Milestone: RC1 for initial release
Component: dashboard |Version:
Resolution: | Keywords:
+-
Comment (by gjm):
Now I look at this again I think I misinterpreted it a little. The patch
appears to avoid the error by not checking that the {{{TicketModule}}} is
active at all. This leaves us using the wrong ticket module and so I see
no advantage in that respect.
As such, I believe any further enhancement that this brings should really
be discussed in a new ticket.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/23#comment:13
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #15: Update styling to Bootstrap
#15: Update styling to Bootstrap + Reporter: jdreimann | Owner: olemis Type: task | Status: new Priority: major | Milestone: Component: dashboard |Version: Resolution: | Keywords: + Comment (by gjm): r1330627 adds a combination of the admin_webui and admin_logging diffs to demonstrate a working page -- Ticket URL: https://issues.apache.org/bloodhound/ticket/15#comment:6 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #15: Update styling to Bootstrap
#15: Update styling to Bootstrap + Reporter: jdreimann | Owner: olemis Type: task | Status: new Priority: major | Milestone: Component: dashboard |Version: Resolution: | Keywords: + Comment (by gjm): r1330630 adds the admin_basics diff given the shear amount of changes involved, it might be better to split this into a number of tickets so that they can be carried out in parallel if others want to help -- Ticket URL: https://issues.apache.org/bloodhound/ticket/15#comment:7 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #15: Update styling to Bootstrap
#15: Update styling to Bootstrap
+
Reporter: jdreimann | Owner: olemis
Type: task | Status: new
Priority: major | Milestone:
Component: dashboard |Version:
Resolution: | Keywords:
+
Comment (by olemis):
Nice to see them in the repos ''':)'''
Added two more patches for plugins and repository admin panels. Thus now
all admin section UI has a bootstrap look and feel.
Plugins admin panel UI looks like shown below. In order to get this done I
had to use Bootstrap 2.0.2 (i.e. upgrade needed) .
[[Image(attachment:bh_theme_x_11_admin_plugins.png, width=600)]]
My patch queue looks like this (beware of the order to apply them ;)
{{{
#!sh
$ hg qapplied
t39/t39_r1328689_indexerror.diff
t23/t23_r1328689_flexible_qct.diff
t15/t15_r1328689_admin_webui.diff
t15/t15_r1328689_admin_logging.diff
t15/t15_r1328689_admin_basics.diff
t15/t15_r1328689_admin_enums.diff
t15/t15_r1328689_admin_perms.diff
t15/t15_r1328689_admin_milestones.diff
t15/t15_r1328689_admin_components.diff
t15/t15_r1328689_admin_versions.diff
t15/t15_r1328689_admin_plugins.diff
t15/t15_r1328689_admin_repositories.diff
}}}
Now I'll move forward and continue with wiki and search templates.
Nonetheless I'll create a new ticket for those . Let's just limit the
scope of this ticket to admin UI.
Is that ok ?
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/15#comment:8
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #43: Include descriptions in Manage Plugins admin panel
#43: Include descriptions in Manage Plugins admin panel + Reporter: olemis | Owner: nobody Type: enhancement | Status: new Priority: major | Milestone: Component: ui design |Version: Keywords: plugin admin panel | + [attachment:ticket:15:t15_r1328689_admin_plugins.diff The patch] attached to #15 so as to implement plugins admin panel does not deal with (collapsible) module and components descriptions . Hence some (professional) design decisions should be made in order to determine what they will look like. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/43 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #15: Update styling to Bootstrap
#15: Update styling to Bootstrap + Reporter: jdreimann | Owner: olemis Type: task | Status: new Priority: major | Milestone: Component: dashboard |Version: Resolution: | Keywords: + Comment (by gjm): r1330928 updates the bootstrap.css to 2.0.3 r1330943 updates bootstrap-dropdown.js to 2.0.3 and adds bootstrap- dropdown.js r1330967 adds the versions admin panel I am delaying further commits as I am not sure that the plugins admin panel works properly so I need to check my patching. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/15#comment:10 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #8: Design Preferences interface
#8: Design Preferences interface
+---
Reporter: jdreimann | Owner: jdreimann
Type: task | Status: new
Priority: minor | Milestone:
Component: dashboard |Version:
Resolution: | Keywords:
+---
Comment (by olemis):
Added some more patches for all preferences panels. Thus now all panels in
prefs section have a candidate bootstrap look and feel.
Sample prefs panel shown below.
[[Image(bh_theme_x_12_prefs_datetime.png, width=600)]]
My patch queue looks like this . Beware of the order to apply them
''';)''' on top of [attachment:ticket:39:t39_r1328689_indexerror.diff
patch for #39] and [attachment:ticket:23:t23_r1328689_flexible_qct.diff
patch for #23] applied on top of r1328689 (which is a rather old version ,
but I thought I'd better submit these as soon as possible)
{{{
#!sh
$ hg qapplied
t39/t39_r1328689_indexerror.diff
t23/t23_r1328689_flexible_qct.diff
t8/t8_r1328689_prefs_webui.diff
t8/t8_r1328689_prefs_general.diff
t8/t8_r1328689_prefs_advanced.diff
t8/t8_r1328689_prefs_datetime.diff
t8/t8_r1328689_prefs_keybindings.diff
t8/t8_r1328689_prefs_pygments.diff
}}}
'''PS: ''' Please edit attachments descriptions . In some cases I
specified #15 by mistake , but #8 should be used instead ... ''':-/'''
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/8#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #10: Design Search Results screen
#10: Design Search Results screen +-- Reporter: jdreimann | Owner: olemis Type: task | Status: assigned Priority: minor | Milestone: Component: dashboard |Version: Resolution: | Keywords: +-- Changes (by olemis): * status: new = assigned * owner: jdreimann = olemis -- Ticket URL: https://issues.apache.org/bloodhound/ticket/10#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #15: Update styling to Bootstrap
#15: Update styling to Bootstrap + Reporter: jdreimann | Owner: olemis Type: task | Status: new Priority: major | Milestone: Component: dashboard |Version: Resolution: | Keywords: + Comment (by gjm): The bootstrap code was not working with the version of jquery that our vendor branch of trac was providing. With trac updating to a version that would work, I have applied the same update to our vendor branch in advance of any decision to update the vendor branch with a newer version of trac. I am therefore able to commit the last of these patches: r1331433 adds the plugins and repositories panels -- Ticket URL: https://issues.apache.org/bloodhound/ticket/15#comment:12 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #42: Disable quick ticket button when user doesn't have sufficient permission
#42: Disable quick ticket button when user doesn't have sufficient permission
--+-
Reporter: jdreimann| Owner: olemis
Type: enhancement | Status: accepted
Priority: major| Milestone: RC1 for initial release
Component: dashboard|Version:
Resolution: | Keywords:
--+-
Comment (by gjm):
I've got a slight change for that - the original patch would result in an
odd change in shape of the button.
{{{
#!diff
Index: templates/bloodhound_theme.html
===
--- templates/bloodhound_theme.html (revision 1331432)
+++ templates/bloodhound_theme.html (working copy)
@@ -120,9 +120,11 @@
py:choose test=
py:when test=qct
div class=btn-group
-a href=# class=btn btn-primary dropdown-toggle
+a href=# py:with=enabled = 'TICKET_CREATE' in perm
+class=btn btn-primary dropdown-toggle ${not enabled
and 'disabled'}
id=qct-newticket rel=popover title=Ticket
-data-content=Alert box data-toggle=dropdown
+data-content=Alert box
+data-toggle=${enabled and 'dropdown' or None}
Create Ticket
/a
div id=qct-box class=dropdown-menu style=width:
300px;
}}}
This will eventually also have to take account of whether it we have
appropriate permissions for the product although I am prepared for that to
be dealt with in a different ticket.
But.. is it me or does it not really have the feeling of being disabled? I
guess that would be because there are no similar buttons to give that kind
of hint.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/42#comment:2
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #42: Disable quick ticket button when user doesn't have sufficient permission
#42: Disable quick ticket button when user doesn't have sufficient permission --+- Reporter: jdreimann| Owner: olemis Type: enhancement | Status: accepted Priority: major| Milestone: RC1 for initial release Component: dashboard|Version: Resolution: | Keywords: --+- Comment (by gjm): I should mention that the above diff would be against r1331432, rather than r1328689 -- Ticket URL: https://issues.apache.org/bloodhound/ticket/42#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #45: Refine XML markup to embed dashboard layouts and widgets
#45: Refine XML markup to embed dashboard layouts and widgets --+ Reporter: olemis| Owner: nobody Type: enhancement | Status: new Priority: minor | Milestone: Component: dashboard |Version: Keywords: markup widget layout genshi template | --+ Right now a combination of XML + JSON has to be inserted in Genshi templates so as to embed widgets and layouts implemented by dashboard plugin . For some reasons it's better to implement this feature using ''XML'' instead. Nonetheless my previous attempt trying to get this done was not as successful as I expected . Further details may be found in comments in Genshi templates included in dashboard plugin -- Ticket URL: https://issues.apache.org/bloodhound/ticket/45 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] BloodhoundDetailedInstallation modified
Page BloodhoundDetailedInstallation was changed by antony
Diff URL:
https://issues.apache.org/bloodhound/wiki/BloodhoundDetailedInstallation?action=diffversion=6
Revision 6
Changes:
---8--8--8--8--8--8--8--8
Index: BloodhoundDetailedInstallation
=
--- BloodhoundDetailedInstallation (version: 5)
+++ BloodhoundDetailedInstallation (version: 6)
@@ -141,7 +141,7 @@
}}}
}}}
||
-|| set {{{$DBSTING}}} ||\
+|| set {{{$DBSTRING}}} ||\
{{{#!td
{{{
export DBSTRING=[db specific string -]
---8--8--8--8--8--8--8--8
--
Page URL:
https://issues.apache.org/bloodhound/wiki/BloodhoundDetailedInstallation
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
This is an automated message. Someone added your email address to be
notified of changes on 'BloodhoundDetailedInstallation' page.
If it was not you, please report to .
[Apache Bloodhound] #47: Investigate enhanced selection of active ticket module (initially for quick ticket)
#47: Investigate enhanced selection of active ticket module (initially for quick ticket) -+- Reporter: gjm | Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Unscheduled Component: dashboard|Version: Keywords: | -+- This issue was originally raised in #23 as the !QuickCreateTicketDialog component was checking the !TicketModule to see whether it was active, ignoring the existence of the overriding !ProductTicketModule. The current fix is to attempt to check against both ticket modules and make sure that only one is active. Note: low priority, please leave until further notice and further clarification. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/47 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #48: Split QuickCreateTicketDialog for more flexible approach
#48: Split QuickCreateTicketDialog for more flexible approach -+- Reporter: gjm | Owner: nobody Type: enhancement | Status: new Priority: trivial | Milestone: Unscheduled Component: dashboard|Version: Keywords: | -+- In order to increase the flexibility of the Quick Ticket functionality, we should consider the patch provided by olemis in [ticket:23#comment:9 #23]: New features are : - Extension point interface `IQuickCreateTicketBackend` . - `DefaultQuickCreateTicketBackend` component implementing the former so as to provide a simple way to create tickets by using Trac built-in components. Used by default in case no other choice is configured in ''trac.ini'' - `ExtensionOption` property used to select active backend. It's not meant to replace your previous implementation but to make the solution flexible and configurable by using Trac built-in mechanisms. The idea is : - Implement a similar backend in multi-product plugin (i.e. reuse your previous code ''';)''' . - Make the installer to set related config option in ''trac.ini'' so as to use multi-product backend since the beginning. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/48 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #15: Update styling to Bootstrap
#15: Update styling to Bootstrap +- Reporter: jdreimann | Owner: olemis Type: task | Status: accepted Priority: major | Milestone: RC1 for initial release Component: dashboard |Version: Resolution: | Keywords: +- Changes (by olemis): * status: new = accepted * milestone: = RC1 for initial release Comment: Should this ticket be closed ? I mean ... Code for all admin panels is committed or not ? If not , what's missing ? -- Ticket URL: https://issues.apache.org/bloodhound/ticket/15#comment:13 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #42: Disable quick ticket button when user doesn't have sufficient permission
#42: Disable quick ticket button when user doesn't have sufficient permission --+- Reporter: jdreimann| Owner: olemis Type: enhancement | Status: accepted Priority: major| Milestone: RC1 for initial release Component: dashboard|Version: Resolution: | Keywords: --+- Comment (by jdreimann): Olemis, I think this is better than before, but I believe the message should be friendlier or at least explain what happened better. When you currently go to the New Ticket screen without the appropriate permissions you get a message saying: TICKET_CREATE privileges are required to perform this operation. You don't have the required permissions. I believe that's the message we should use, if possible from the same origin. The alert should be of the alert-info type, because we're just relaying some information - no need to issue an alert-'''error'''. Personally I would also drop the 'forbidden' label completely. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/42#comment:7 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #46: Bootstrap icons missing
#46: Bootstrap icons missing +- Reporter: olemis | Owner: olemis Type: defect | Status: closed Priority: major | Milestone: RC1 for initial release Component: ui design |Version: Resolution: fixed | Keywords: bootstrap +- Changes (by gjm): * status: accepted = closed * resolution: = fixed Comment: r1332705 applies the change to the bootstrap.css provided by Olemis -- Ticket URL: https://issues.apache.org/bloodhound/ticket/46#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #49: Allow bootstrap to be used without the need to change it.
#49: Allow bootstrap to be used without the need to change it. -+ Reporter: gjm | Owner: nobody Type: enhancement | Status: new Priority: minor| Milestone: Component: dashboard|Version: Keywords: | -+ #46 noted a regression due to the bootstrap.css needing to be adjusted to suit our directory structure. I would prefer to use an unpatched version of bootstrap.css if possible which suggests that bootstrap might be better contained as a whole within its own directory. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/49 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #10: Design Search Results screen
#10: Design Search Results screen +-- Reporter: jdreimann | Owner: olemis Type: task | Status: assigned Priority: minor | Milestone: Component: dashboard |Version: Resolution: | Keywords: +-- Comment (by olemis): As a result search page looks like this [[Image(bh_theme_x_13_search.png, width=600px)]] -- Ticket URL: https://issues.apache.org/bloodhound/ticket/10#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #10: Design Search Results screen
#10: Design Search Results screen +-- Reporter: jdreimann | Owner: gjm Type: task | Status: accepted Priority: minor | Milestone: Component: dashboard |Version: Resolution: | Keywords: +-- Changes (by gjm): * owner: olemis = gjm * status: assigned = accepted Comment: Claiming ticket for the purposes of reviewing -- Ticket URL: https://issues.apache.org/bloodhound/ticket/10#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #50: Implement ticket view
#50: Implement ticket view ---+- Reporter: gjm| Owner: jdreimann Type: task | Status: new Priority: major | Milestone: RC1 for initial release Component: dashboard |Version: Keywords: | ---+- Current design is in https://svn.apache.org/repos/asf/incubator/bloodhound/trunk/doc/html- templates/ticket.html -- Ticket URL: https://issues.apache.org/bloodhound/ticket/50 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #52: Design Preferences interface
#52: Design Preferences interface ---+- Reporter: gjm| Owner: nobody Type: defect | Status: new Priority: minor | Milestone: Unscheduled Component: ui design |Version: Keywords: | ---+- https://issues.apache.org/bloodhound/wiki/Ui/Preferences (Was #8) -- Ticket URL: https://issues.apache.org/bloodhound/ticket/52 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #8: Update styling for preferences to bootstrap (was: Design Preferences interface)
#8: Update styling for preferences to bootstrap +- Reporter: jdreimann | Owner: olemis Type: task | Status: assigned Priority: minor | Milestone: RC1 for initial release Component: dashboard |Version: Resolution: | Keywords: +- Changes (by gjm): * milestone: = RC1 for initial release Old description: https://issues.apache.org/bloodhound/wiki/Ui/Preferences New description: This page has no changes for initial release other than applying bootstrap styling changes Effectively spawned from #15 -- Comment: This ticket is now for the preferences styling changes associated with #15 before a new page is available. Changing title and raising new ticket for design work, which is now in #52 -- Ticket URL: https://issues.apache.org/bloodhound/ticket/8#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #54: Update styling for reports to bootstrap
#54: Update styling for reports to bootstrap ---+- Reporter: gjm| Owner: nobody Type: task | Status: new Priority: major | Milestone: RC1 for initial release Component: dashboard |Version: Keywords: | ---+- This page has no changes for initial release other than applying bootstrap styling changes Spawned from #15 -- Ticket URL: https://issues.apache.org/bloodhound/ticket/54 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #56: Catch-all for updates to bootstrap.
#56: Catch-all for updates to bootstrap. +- Reporter: gjm| Owner: nobody Type: task | Status: new Priority: minor | Milestone: RC1 for initial release Component: dashboard |Version: Resolution: | Keywords: +- Description changed by gjm: Old description: A number of pages will not be provided with new designs ready for implementation for the initial release. These should be updated to use bootstrap. There are already specific tickets for updating: * Search Results: #55 * Reports: #54 * Login: #53 * Custom Query: #51 * Preferences: #8 * Admin: #15 Once the above tickets are complete, go searching for more templates to update. New description: A number of pages will not be provided with new designs ready for implementation for the initial release. These should be updated to use bootstrap. There are already specific tickets for updating: * Search Results: #10 * Reports: #54 * Login: #53 * Custom Query: #51 * Preferences: #8 * Admin: #15 Once the above tickets are complete, go searching for more templates to update. -- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/56#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #50: Implement ticket view
#50: Implement ticket view +- Reporter: gjm| Owner: jdreimann Type: task | Status: new Priority: major | Milestone: RC1 for initial release Component: dashboard |Version: Resolution: | Keywords: +- Comment (by jdreimann): I've updated the style now (r1332992) , so it should be good to go. I'd just like to reiterate that the way it looks should be a close match once implemented, but some of the code is messy: - There's an empty div with a fixed height to push the footer further down - The way the relative date/time is aligned in comments isn't viable - they stick out of the application frame on the left. - The comment box is not a full 100% wide, which it should be. This may be because it has to be wrapped in a form to achieve this, but I'm not sure. The actual implementation should fix these three issues, and I'm open to suggestions on how to fix them in the mockups too. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/50#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #37: Product and products pages
#37: Product and products pages ---+-- Reporter: gjm | Owner: gjm Type: task | Status: assigned Priority: major | Milestone: Component: multiproduct |Version: Resolution:| Keywords: ---+-- Changes (by gjm): * owner: nobody = gjm * status: new = assigned -- Ticket URL: https://issues.apache.org/bloodhound/ticket/37#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #41: Wiki edit side-by-side doesn't work
#41: Wiki edit side-by-side doesn't work +- Reporter: jdreimann | Owner: olemis Type: defect | Status: accepted Priority: major | Milestone: RC1 for initial release Component: ui design |Version: Resolution: | Keywords: wiki bootstrap +- Comment (by gjm): Replying to [comment:2 olemis]: Would it be best for me (or another committer) to evaluate what you have managed here so far so that others can help fix any more from this? -- Ticket URL: https://issues.apache.org/bloodhound/ticket/41#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #16: Add functionality equivalent to 'ticket status by' progress bars into Milestone
#16: Add functionality equivalent to 'ticket status by' progress bars into Milestone --+- Reporter: gjm | Owner: jdreimann Type: enhancement | Status: new Priority: major| Milestone: RC1 for initial release Component: dashboard|Version: Resolution: | Keywords: --+- Old description: see right hand side of milestone:milestone1 for example of display lost from the design New description: see right hand side of milestone:RC1 for initial release for example of display lost from the design -- Comment (by gjm): Updated to provide a working link. I assume that this is still a valid ticket. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/16#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #41: Wiki edit side-by-side doesn't work
#41: Wiki edit side-by-side doesn't work +- Reporter: jdreimann | Owner: olemis Type: defect | Status: accepted Priority: major | Milestone: RC1 for initial release Component: ui design |Version: Resolution: | Keywords: wiki bootstrap +- Comment (by olemis): Well ... these Genshi templates are not trivial . What else (besides repeated Tabular Unified tabs) needs to be fixed ? Please feel free to change or enhance any patch I submit and don't hesitate to ask in case you have any doubts ''';)''' -- Ticket URL: https://issues.apache.org/bloodhound/ticket/41#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #41: Wiki edit side-by-side doesn't work
#41: Wiki edit side-by-side doesn't work +- Reporter: jdreimann | Owner: olemis Type: defect | Status: accepted Priority: major | Milestone: RC1 for initial release Component: ui design |Version: Resolution: | Keywords: wiki bootstrap +- Comment (by olemis): So far I've only improved `wiki_view.html` and `wiki_edit.html` templates (which are the ones related to this defect) . Further changes to other wiki templates will be implemented in #58 . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/41#comment:5 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #41: Wiki edit side-by-side doesn't work
#41: Wiki edit side-by-side doesn't work +- Reporter: jdreimann | Owner: olemis Type: defect | Status: accepted Priority: major | Milestone: RC1 for initial release Component: ui design |Version: Resolution: | Keywords: wiki bootstrap +- Comment (by gjm): Replying to [comment:4 olemis]: Well ... these Genshi templates are not trivial . I can tell! What else (besides repeated Tabular Unified tabs) needs to be fixed ? Those were the things I was referring to. I don't mind this being incomplete if we raise a new ticket which can be assessed for priority. Does that sound good? -- Ticket URL: https://issues.apache.org/bloodhound/ticket/41#comment:6 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #62: Term Paper Shut Down
#62: Term Paper Shut Down ---+ Reporter: georgiarhodes | Owner: nobody Type: defect | Status: new Priority: minor | Milestone: Component: dashboard |Version: Keywords: | ---+ I really don't have any plan of [http://www.superiorpapers.com/term_paper.php buying a term paper] but I bought one because my computer shut down. I don't have the patience to do my assignments at school. Please fix my computer now. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/62 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] Deleted User: georgiarhodes
Deleted User for user georgiarhodes -- Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #62: Term Paper Shut Down
#62: Term Paper Shut Down + Reporter: georgiarhodes | Owner: nobody Type: defect | Status: closed Priority: minor | Milestone: Component: dashboard |Version: Resolution: invalid| Keywords: + Changes (by gjm): * status: new = closed * resolution: = invalid Old description: I really don't have any plan of [http://www.superiorpapers.com/term_paper.php buying a term paper] but I bought one because my computer shut down. I don't have the patience to do my assignments at school. Please fix my computer now. New description: I really don't have any plan of (edit: suspicious link removed) buying a term paper but I bought one because my computer shut down. I don't have the patience to do my assignments at school. Please fix my computer now. -- Comment: This issue appears to have no relevance to bloodhound. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/62#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #37: Product and products pages
#37: Product and products pages ---+-- Reporter: gjm | Owner: gjm Type: task | Status: assigned Priority: major | Milestone: Component: multiproduct |Version: Resolution:| Keywords: ---+-- Comment (by gjm): r1334065 adds basic processing and templates for these -- Ticket URL: https://issues.apache.org/bloodhound/ticket/37#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #41: Wiki edit side-by-side doesn't work
#41: Wiki edit side-by-side doesn't work
+-
Reporter: jdreimann | Owner: olemis
Type: defect | Status: accepted
Priority: major | Milestone: RC1 for initial release
Component: ui design |Version:
Resolution: | Keywords: wiki bootstrap
+-
Comment (by olemis):
I've updated my patch queue so as to build patches against a more recent
version r1333006 . I'm submitting updated patches that need to be applied
in the order shown below (notice that alternate links patch does not
change at all , so it keeps old rev number in it's name ;) :
{{{
#!sh
$ hg qapplied
t41/t41_r1331433_altlinks.diff
t41/t41_r1333006_keep_trac_css.diff
t41/t41_r1333006_wiki_edit.diff
t41/t41_r1333006_wiki_view.diff
}}}
Feedback appreciated ... though everything should work exactly the same as
before ... this is more like a bureaucratic update ''';)'''
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/41#comment:8
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #58: Update pending wiki templates
#58: Update pending wiki templates
+-
Reporter: olemis | Owner: olemis
Type: task | Status: accepted
Priority: major | Milestone: RC1 for initial release
Component: ui design |Version:
Resolution: | Keywords: wiki bootstrap
+-
Changes (by olemis):
* status: new = accepted
Comment:
Attached patches implement the following features :
- Wiki history view
- Wiki diff view
- Rename Wiki page form
- Delete wiki page form
Patches are built on top of those already attached to #41 . This fact
becomes evident after taking a look to patch order .
{{{
#!sh
$ hg qapplied
t41/t41_r1331433_altlinks.diff
t41/t41_r1333006_keep_trac_css.diff
t41/t41_r1333006_wiki_edit.diff
t41/t41_r1333006_wiki_view.diff
t58/t58_r1333006_wiki_rename.diff
t58/t58_r1333006_wiki_delete.diff
t58/t58_r1333006_wiki_diff.diff
}}}
Once they are applied against r1333006 , different parts of the web UI
look like shown below
[[Image(bh_theme_x_19_wiki_diff.png, width=600)]]
[[Image(bh_theme_x_20_wiki_history.png, width=600)]]
Please review .
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/58#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #50: Implement ticket view
#50: Implement ticket view +- Reporter: gjm| Owner: olemis Type: task | Status: accepted Priority: critical | Milestone: RC1 for initial release Component: dashboard |Version: Resolution: | Keywords: +- Changes (by olemis): * owner: unassigned = olemis * status: assigned = accepted * cc: olemis+bh@… (added) -- Ticket URL: https://issues.apache.org/bloodhound/ticket/50#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #50: Implement ticket view
#50: Implement ticket view +- Reporter: gjm| Owner: olemis Type: task | Status: accepted Priority: critical | Milestone: RC1 for initial release Component: dashboard |Version: Resolution: | Keywords: ticket bootstrap +- Changes (by olemis): * keywords: = ticket bootstrap Comment: I started to review this ticket so as to provide Genshi template(s) implementing bootstrap styles, controls , best practices ... just like before (e.g. #15 , #41 , #10 , #8 , #58 , #59 ) . In order to get this done IMO first we should decide what to do with the following subjects : 1. Decide how to implement in-place edit . a. Will we use ''jEditable'' ? b. Otherwise what other js framework | library will be used ? 1. This is a task illustrating that we really should move forward with #40 and merge theme and dashboard plugins into a single '''Bloodhound UI''' plugin. I look forward to your comments . It seems I really cannot start working on this until I know what's going to happen with subjects above . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/50#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #40: Merge existing plugins into a single Bloodhound UI plugin
#40: Merge existing plugins into a single Bloodhound UI plugin --+--- Reporter: olemis | Owner: nobody Type: enhancement | Status: new Priority: minor| Milestone: Component: dashboard|Version: Resolution: | Keywords: dashboard theme merge --+--- Comment (by gjm): We shouldn't be repeating code. It would be nice to separate out theme and UI but if it is turning out that these are the same thing, we can combine these. The alternative would be to separate out the common parts and either put them into the trac core code or a component that both theme and dashboard rely on. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/40#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #50: Implement ticket view
#50: Implement ticket view +- Reporter: gjm| Owner: olemis Type: task | Status: accepted Priority: critical | Milestone: RC1 for initial release Component: dashboard |Version: Resolution: | Keywords: ticket bootstrap +- Comment (by gjm): Does this ticket specifically require the in-place edit code. Given that we cannot guarantee js being active, perhaps we should make sure that we get a reasonable experience without the in-place editing before considering this feature? My current thoughts on the second point are put in ticket:40#comment:2 - we do need a quick resolution for this if it is likely to hold up work. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/50#comment:5 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #51: Update styling for custom query to bootstrap
#51: Update styling for custom query to bootstrap +- Reporter: gjm| Owner: nobody Type: task | Status: new Priority: major | Milestone: RC1 for initial release Component: dashboard |Version: Resolution: | Keywords: +- Comment (by olemis): In order to provide Genshi template(s) implementing bootstrap styles, controls , best practices ... just like before (e.g. #15 , #41 , #10 , #8 , #58 , #59 ) I think we really should move forward with #40 and merge theme and dashboard plugins into a single '''Bloodhound UI''' plugin. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/51#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #54: Update styling for reports to bootstrap
#54: Update styling for reports to bootstrap +- Reporter: gjm| Owner: nobody Type: task | Status: new Priority: major | Milestone: RC1 for initial release Component: dashboard |Version: Resolution: | Keywords: +- Comment (by olemis): In order to provide Genshi template(s) implementing bootstrap styles, controls , best practices ... just like before (e.g. #15 , #41 , #10 , #8 , #58 , #59 ) I think we really should move forward with #40 and merge theme and dashboard plugins into a single '''Bloodhound UI''' plugin. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/54#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #40: Merge existing plugins into a single Bloodhound UI plugin
#40: Merge existing plugins into a single Bloodhound UI plugin --+--- Reporter: olemis | Owner: nobody Type: enhancement | Status: new Priority: minor| Milestone: Component: dashboard|Version: Resolution: | Keywords: dashboard theme merge --+--- Comment (by olemis): Related to #51 #54 -- Ticket URL: https://issues.apache.org/bloodhound/ticket/40#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #40: Merge existing plugins into a single Bloodhound UI plugin
#40: Merge existing plugins into a single Bloodhound UI plugin --+--- Reporter: olemis | Owner: nobody Type: enhancement | Status: new Priority: minor| Milestone: Component: dashboard|Version: Resolution: | Keywords: dashboard theme merge --+--- Comment (by gjm): I don't understand why #51 and #54 are dependent on a decision on this ticket. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/40#comment:5 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #41: Wiki edit side-by-side doesn't work
#41: Wiki edit side-by-side doesn't work +- Reporter: jdreimann | Owner: gjm Type: defect | Status: accepted Priority: major | Milestone: RC1 for initial release Component: ui design |Version: Resolution: | Keywords: wiki bootstrap +- Changes (by gjm): * owner: olemis = gjm Comment: Accepting ticket to study patches and commit. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/41#comment:9 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #41: Wiki edit side-by-side doesn't work
#41: Wiki edit side-by-side doesn't work +- Reporter: jdreimann | Owner: gjm Type: defect | Status: accepted Priority: major | Milestone: RC1 for initial release Component: ui design |Version: Resolution: | Keywords: wiki bootstrap +- Comment (by gjm): I have patched without modification to those provided by Olemis. r1335431 styles for alternate download links section using bootstrap r1335442 allow exceptions in removing trac css r1335445 fixing side by side edit r1335448 updating wiki view to use bootstrap -- Ticket URL: https://issues.apache.org/bloodhound/ticket/41#comment:10 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #41: Wiki edit side-by-side doesn't work
#41: Wiki edit side-by-side doesn't work +- Reporter: jdreimann | Owner: gjm Type: defect | Status: closed Priority: major | Milestone: RC1 for initial release Component: ui design |Version: Resolution: fixed | Keywords: wiki bootstrap +- Changes (by gjm): * status: accepted = closed * resolution: = fixed Comment: Calling this fixed - I expect more tickets to result from this set of views. Please raise as appropriate. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/41#comment:11 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #58: Update pending wiki templates
#58: Update pending wiki templates +- Reporter: olemis | Owner: gjm Type: task | Status: accepted Priority: major | Milestone: RC1 for initial release Component: ui design |Version: Resolution: | Keywords: wiki bootstrap +- Changes (by gjm): * owner: olemis = gjm Comment: accepted for review -- Ticket URL: https://issues.apache.org/bloodhound/ticket/58#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #40: Merge existing plugins into a single Bloodhound UI plugin
#40: Merge existing plugins into a single Bloodhound UI plugin --+--- Reporter: olemis | Owner: nobody Type: enhancement | Status: new Priority: minor| Milestone: Component: dashboard|Version: Resolution: | Keywords: dashboard theme merge --+--- Comment (by gjm): I can see what you mean but I think we may need some time to investigate whether there is a way for us to decouple the plugins enough to resolve this problem. In the short term, the quickest solution (of sorts) would be to make one or the other plugin a dependency so that there is some guarantee of code, templates and resources being available. If such a package dependency is created, we should leave this ticket open to drive the discussion of a more permanent solution. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/40#comment:7 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #40: Merge existing plugins into a single Bloodhound UI plugin
#40: Merge existing plugins into a single Bloodhound UI plugin --+--- Reporter: olemis | Owner: nobody Type: enhancement | Status: new Priority: minor| Milestone: Component: dashboard|Version: Resolution: | Keywords: dashboard theme merge --+--- Comment (by gjm): r1336588 adds the glyphicons to dashboard r1336707 makes the theme dependent on dashboard being available and adds the milestone view to the theme plugin r1336709 removes the milestone view from the dashboard -- Ticket URL: https://issues.apache.org/bloodhound/ticket/40#comment:9 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] WikiStart modified
Page WikiStart was changed by SophieZelmani
Diff URL:
https://issues.apache.org/bloodhound/wiki/WikiStart?action=diffversion=8
Revision 8
Comment: fixed
Changes:
---8--8--8--8--8--8--8--8
Index: WikiStart
=
--- WikiStart (version: 7)
+++ WikiStart (version: 8)
@@ -40,5 +40,8 @@
* WikiFormatting: Wiki formatting documentation.
Find out more in our Wiki:
-
+{{{
+#!html
+h5 style=text-align: right; color: #FFa style=border-bottom: 0px;
href=http://www.5hiva.com/mother-of-the-bride-dresses-mother-of-the-groom-dresses/;
rel=dofollow title=mother of the bride dressesmother of the bride
dresses/a/h5
+}}}
[[TitleIndex(format=hierarchy,min=4,include=Ui*:Multi*:Blood*)]]
---8--8--8--8--8--8--8--8
--
Page URL: https://issues.apache.org/bloodhound/wiki/WikiStart
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
This is an automated message. Someone added your email address to be
notified of changes on 'WikiStart' page.
If it was not you, please report to .
[Apache Bloodhound] Deleted User: SophieZelmani
Deleted User for user SophieZelmani -- Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] WikiStart deleted version
Version 8 of page WikiStart was deleted by gjm -- Page URL: https://issues.apache.org/bloodhound/wiki/WikiStart Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker This is an automated message. Someone added your email address to be notified of changes on 'WikiStart' page. If it was not you, please report to .
[Apache Bloodhound] WikiStart modified
Page WikiStart was changed by SophieZelmani
Diff URL:
https://issues.apache.org/bloodhound/wiki/WikiStart?action=diffversion=8
Revision 8
Changes:
---8--8--8--8--8--8--8--8
Index: WikiStart
=
--- WikiStart (version: 7)
+++ WikiStart (version: 8)
@@ -42,3 +42,7 @@
Find out more in our Wiki:
[[TitleIndex(format=hierarchy,min=4,include=Ui*:Multi*:Blood*)]]
+{{{
+#!html
+h5 style=text-align: right; color: #FFa style=border-bottom: 0px;
href=http://www.5hiva.com/mother-of-the-bride-dresses-mother-of-the-groom-dresses/;
rel=dofollow title=mother of the bride dressesmother of the bride
dresses/a/h5
+}}}
---8--8--8--8--8--8--8--8
--
Page URL: https://issues.apache.org/bloodhound/wiki/WikiStart
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
This is an automated message. Someone added your email address to be
notified of changes on 'WikiStart' page.
If it was not you, please report to .
[Apache Bloodhound] WikiStart deleted version
Version 8 of page WikiStart was deleted by gjm -- Page URL: https://issues.apache.org/bloodhound/wiki/WikiStart Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker This is an automated message. Someone added your email address to be notified of changes on 'WikiStart' page. If it was not you, please report to .
[Apache Bloodhound] #63: Bootstrap styles of ticket changelog not applied after AJAX preview
#63: Bootstrap styles of ticket changelog not applied after AJAX preview +-- Reporter: olemis | Owner: olemis Type: defect | Status: new Priority: critical| Milestone: RC1 for Component: ui design | initial release Keywords: ticket changelog comment bootstrap |Version: +-- After applying patches implementing #50 , ticket change log (i.e. comments and threads) looks like expected on load . Nonetheless once it's updated later in order to preview pending changes , old markup and styles are applied instead ... ... at the moment I don't know what's causing this ... -- Ticket URL: https://issues.apache.org/bloodhound/ticket/63 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #54: Update styling for reports to bootstrap
#54: Update styling for reports to bootstrap +- Reporter: gjm| Owner: olemis Type: task | Status: accepted Priority: major | Milestone: RC1 for initial release Component: dashboard |Version: Resolution: | Keywords: +- Changes (by olemis): * owner: nobody = olemis * status: new = accepted -- Ticket URL: https://issues.apache.org/bloodhound/ticket/54#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #63: Bootstrap styles of ticket changelog not applied after AJAX preview
#63: Bootstrap styles of ticket changelog not applied after AJAX preview + Reporter: olemis | Owner: olemis Type: defect | Status: accepted Priority: critical | Milestone: RC1 for initial release Component: ui design |Version: Resolution: | Keywords: ticket changelog comment bootstrap + Changes (by olemis): * status: new = accepted -- Ticket URL: https://issues.apache.org/bloodhound/ticket/63#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #64: Reduce the scope of rules in timeline.css
#64: Reduce the scope of rules in timeline.css -+- Reporter: olemis | Owner: olemis Type: defect | Status: new Priority: minor| Milestone: RC1 for initial release Component: ui design|Version: Keywords: timeline css styles | -+- Styles applied to activity feed widget , as they are written today, modify the look and feel of elements outside widget boundaries . It's necessary to limit the scope of the aforementioned rules by specifying `.timeline` class , which is inserted in top level widget `content` pane . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/64 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #64: Reduce the scope of rules in timeline.css
#64: Reduce the scope of rules in timeline.css --+- Reporter: olemis | Owner: olemis Type: enhancement | Status: new Priority: minor| Milestone: RC1 for initial release Component: ui design|Version: Resolution: | Keywords: timeline css styles --+- Changes (by olemis): * type: defect = enhancement -- Ticket URL: https://issues.apache.org/bloodhound/ticket/64#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #50: Implement ticket view
#50: Implement ticket view
+-
Reporter: gjm| Owner: olemis
Type: task | Status: accepted
Priority: critical | Milestone: RC1 for initial release
Component: dashboard |Version:
Resolution: | Keywords: ticket bootstrap
+-
Comment (by olemis):
Please '''in dashboard plugin''' apply
[attachment:t50_r1328362_widget_macros_nocomment.diff another patch]
fixing a minor issue . Apply it on top of the patches uploaded to
implement #40 ( against r1328362 ). Consider this order :
{{{
#!sh
$ hg qapplied
t40/t40_r1328362_duplicate_webui.diff
t40/t40_r1328362_glyphicons_dashboard.diff
t40/t40_r1328362_remove_milestone_view.diff
t50/t50_r1328362_widget_macros_nocomment.diff
}}}
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/50#comment:9
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #64: Reduce the scope of rules in timeline.css
#64: Reduce the scope of rules in timeline.css --+- Reporter: olemis | Owner: olemis Type: enhancement | Status: accepted Priority: minor| Milestone: RC1 for initial release Component: dashboard|Version: Resolution: | Keywords: timeline css styles --+- Changes (by olemis): * status: new = accepted * component: ui design = dashboard -- Ticket URL: https://issues.apache.org/bloodhound/ticket/64#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #64: Reduce the scope of rules in timeline.css
#64: Reduce the scope of rules in timeline.css
--+-
Reporter: olemis | Owner: olemis
Type: enhancement | Status: accepted
Priority: minor| Milestone: RC1 for initial release
Component: dashboard|Version:
Resolution: | Keywords: timeline css styles
--+-
Comment (by olemis):
This patch is built on top of those implementing changes in ticket web UI
(dashboard plugin) as this issue was discovered while testing the solution
for #50 . Therefore they should be applied in order shown below :
{{{
#!sh
$ hg qapplied
t40/t40_r1328362_duplicate_webui.diff
t40/t40_r1328362_glyphicons_dashboard.diff
t40/t40_r1328362_remove_milestone_view.diff
t50/t50_r1328362_widget_macros_nocomment.diff
t64/t64_r1328362_timeline_css.diff
}}}
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/64#comment:3
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #50: Implement ticket view
#50: Implement ticket view +- Reporter: gjm| Owner: olemis Type: task | Status: accepted Priority: critical | Milestone: RC1 for initial release Component: dashboard |Version: Resolution: | Keywords: ticket bootstrap +- Comment (by olemis): Screenshots illustrate how ticket web UI looks like after applying patches mentioned above. [[Image(bh_theme_x_23_ticket_box_attachments.png, width=600)]] [[Image(bh_theme_x_24_ticket_changelog.png, width=600)]] [[Image(bh_theme_x_25_ticket_modify.png, width=600)]] -- Ticket URL: https://issues.apache.org/bloodhound/ticket/50#comment:10 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #65: Sticky panels in Bloodhound theme
#65: Sticky panels in Bloodhound theme -+ Reporter: olemis | Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: ui design|Version: Keywords: bootstrap| -+ Implement sticky panels sketched in [https://svn.apache.org/repos/asf/incubator/bloodhound/trunk/doc/html- templates/ mockups] . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/65 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #66: Fix report results table when including full row fields
#66: Fix report results table when including full row fields
---+-
Reporter: olemis | Owner: olemis
Type: defect | Status: new
Priority: critical | Milestone: RC1 for initial release
Component: dashboard |Version:
Keywords: reports bootstrap |
---+-
After applying patches submitted to #54 still an issue happens when
rendering reports including full row fields (e.g. {5} ) . Attached
screenshot illustrates the defect .
'''PS:''' I'm submitting this separate ticket so as to be able to apply
patches in #54 asap and close that ticket introducing most of reports web
UI logic working as expected (except for minor issues like this ...
''':-/''' ).
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/66
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #54: Update styling for reports to bootstrap
#54: Update styling for reports to bootstrap
+-
Reporter: gjm| Owner: olemis
Type: task | Status: accepted
Priority: major | Milestone: RC1 for initial release
Component: dashboard |Version:
Resolution: | Keywords:
+-
Comment (by olemis):
Attached patches implement most of report view .
Theme
Please apply patches in order shown below against r1336707 .
{{{
#!sh
$ hg qapplied
t54/t54_r1336707_report_list.diff
t54/t54_r1336707_report_view.diff
}}}
Dashboard
Only needed to apply [attachment:t54_r1336709_grid_template_updates.diff]
against r1336709 .
{{{
#!sh
$ hg qapplied
t54/t54_r1336709_grid_template_updates.diff
}}}
This patch is needed when applying
[attachment:t54_r1336707_report_view.diff] in order to see `empty` label
in groups when e.g. optional field is blank (take a look at
[attachment:t54_r1336707_report_view.diff screenshot]) .
[[Image(bh_theme_x_26_reports_list.png, width=600)]]
[[Image(bh_theme_x_27_report_6.png, width=600)]]
Pending templates will be delivered in few minutes ... so , please do not
close this ticket yet ''';)'''
Side effects
[attachment:t54_r1336707_report_view.diff This patch] introduces [#66 this
issue]
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/54#comment:3
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #66: Fix report results table when including full row fields
#66: Fix report results table when including full row fields +- Reporter: olemis | Owner: olemis Type: defect | Status: new Priority: critical | Milestone: RC1 for initial release Component: dashboard |Version: Resolution: | Keywords: reports bootstrap +- Comment (by olemis): [[Image(bh_theme_x_28_report_5_wrong.png, width=600)]] -- Ticket URL: https://issues.apache.org/bloodhound/ticket/66#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #67: Highlight tickets outputted by reports
#67: Highlight tickets outputted by reports --+ Reporter: olemis| Owner: nobody Type: enhancement | Status: new Priority: major | Milestone: Component: ui design |Version: Keywords: reports highlighting | --+ Previous highlighting support for ticket rows has been lost . It'd be nice to figure out how to do it under the new circumstances . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/67 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #54: Update styling for reports to bootstrap
#54: Update styling for reports to bootstrap
+-
Reporter: gjm| Owner: olemis
Type: task | Status: accepted
Priority: major | Milestone: RC1 for initial release
Component: dashboard |Version:
Resolution: | Keywords:
+-
Comment (by olemis):
Two more patches for theme have been uploaded . Please apply them in the
following order (and don't forget to consider
[attachment:t54_r1336709_grid_template_updates.diff previous patch] for
dashboard plugin as [comment:3 mentioned before] ) :
{{{
#!sh
$ hg qapplied
t54/t54_r1336707_report_list.diff
t54/t54_r1336707_report_view.diff
t54/t54_r1336709_report_delete.diff
t54/t54_r1336709_report_edit.diff
}}}
... feel free to close this ticket now if appropriate .
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/54#comment:4
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #68: Dashboard should show times in a nice format than datetime
#68: Dashboard should show times in a nice format than datetime
--+
Reporter: gjm | Owner: nobody
Type: enhancement | Status: new
Priority: major| Milestone:
Component: dashboard|Version:
Resolution: | Keywords:
--+
Comment (by gjm):
A possible fix (suggestion from a while back via Olemis) is to make the
following change to trac core:
{{{
#!diff
Index: trac/trac/ticket/query.py
===
--- trac/trac/ticket/query.py (revision 184)
+++ trac/trac/ticket/query.py (working copy)
@@ -34,8 +34,9 @@
from trac.ticket.api import TicketSystem
from trac.ticket.model import Milestone, group_milestones
from trac.util import Ranges, as_bool
-from trac.util.datefmt import format_datetime, from_utimestamp,
parse_date, \
- to_timestamp, to_utimestamp, utc, user_time
+from trac.util.datefmt import format_date, format_datetime,
from_utimestamp, \
+ parse_date, to_timestamp, to_utimestamp,
utc, \
+ user_time
from trac.util.presentation import Paginator
from trac.util.text import empty, shorten_line, quote_query_string
from trac.util.translation import _, tag_, cleandoc_
@@ -753,6 +754,9 @@
ticket['changed'] = True
if self.group:
group_key = ticket[self.group]
+# If grouping by datetime field use days rather than time
+if self.group in ('changetime', 'time'):
+group_key = format_date(group_key)
groups.setdefault(group_key, []).append(ticket)
if not groupsequence or group_key not in groupsequence:
groupsequence.append(group_key)
}}}
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/68#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #68: Dashboard should show times in a nice format than datetime
#68: Dashboard should show times in a nice format than datetime --+- Reporter: gjm | Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: RC1 for initial release Component: dashboard|Version: Resolution: | Keywords: --+- Changes (by gjm): * milestone: = RC1 for initial release -- Ticket URL: https://issues.apache.org/bloodhound/ticket/68#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #69: enable ticket details in timeline
#69: enable ticket details in timeline
-+
Reporter: gjm | Owner: nobody
Type: enhancement | Status: new
Priority: major| Milestone:
Component: dashboard|Version:
Keywords: |
-+
Adding
{{{
#!ini
[timeline]
ticket_show_details = true
abbreviated_messages = true
}}}
to the base.ini will allow ticket events other than just tickets opening
and closing to be shown in the timeline which seems like a good thing.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/69
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #70: Make sure comments in genshi templates are appropriate or hide them
#70: Make sure comments in genshi templates are appropriate or hide them
---+
Reporter: gjm| Owner: nobody
Type: task | Status: new
Priority: major | Milestone:
Component: dashboard |Version:
Keywords: |
---+
Consider changing comments to use {{{!--!}}} to stop inappropriate
comments appearing in the html. For example, comments that provide example
snippets for developers should not be rendered.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/70
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #50: Implement ticket view
#50: Implement ticket view +- Reporter: gjm| Owner: olemis Type: task | Status: accepted Priority: critical | Milestone: RC1 for initial release Component: dashboard |Version: Resolution: | Keywords: ticket bootstrap +- Comment (by gjm): r1338129 applies the ticket.diff patch (textarea_padding.diff largely ignored as it mostly touched unrelated files) widget_macros_nocomment.diff does not really belong here so creating a general comment cleanup ticket for it to be a part of - #70 -- Ticket URL: https://issues.apache.org/bloodhound/ticket/50#comment:11 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
