Edgewall Software
Modify

Opened 13 years ago

Last modified 7 months ago

#1 new enhancement

Add a new project summary module.

Reported by: (none) Owned by:
Priority: high Milestone: topic-multiproject
Component: general Version: 0.6.1
Severity: critical Keywords: multiproject
Cc: a.a.vykhodtsev@…, lists@…, itamarost@…, tn@…, leho@…, Ryan J Ollos
Release Notes:
API Changes:

Description (last modified by Christian Boos)

This module should useful information like:

  • Number of open tickets
  • Tickets targeted for each milestone
  • Tickets assigned to the current user (but see rather #4588 for that)
  • And more…

… like a project description, attachments, etc.

Attachments (0)

Change History (49)

comment:1 Changed 13 years ago by Jonas Borgström

Priority: p1p2

comment:2 Changed 13 years ago by daniel

Milestone: 2.0
Priority: highnormal
Version: devel

Ah. bug #1… hehe.. this one will be here a while, or slowly die..

comment:3 Changed 13 years ago by daniel

Severity: normalenhancement

comment:4 Changed 12 years ago by daniel

Milestone: 2.00.8
Priority: normalhighest

comment:5 Changed 12 years ago by daniel

Milestone: 0.81.0

comment:6 Changed 12 years ago by anonymous

Personally…

I think actually leaving a COMMENT as to why you made a change to this ticket number!

Going from high priority to low and back makes no sense with out an explanation!!!

comment:7 Changed 12 years ago by daniel

Milestone: 1.02.0

This is a pretty vague ticket. Lets close it.

comment:8 Changed 12 years ago by daniel

The idea is central for the redesign, but needs to be fleshed out somewhere else.

comment:9 Changed 11 years ago by Christian Boos

Milestone: 2.01.0
Priority: highnormal

I wonder if this could not be done with a set of wiki macros: with the [[TicketQuery()]] and the WikiInclude macro to be able to include the WikiStart, it should be possible to compose something like a dynamic My Page.

Note: it would be useful to be able to delete all the test comments attached to this ticket…

comment:10 Changed 11 years ago by anonymous

Component: generallog view

123

comment:11 Changed 11 years ago by Matthew Good

Component: log viewgeneral

comment:12 Changed 11 years ago by anonymous

Component: generalchangeset view

comment:13 Changed 11 years ago by anonymous

Component: changeset viewproject
Owner: changed from Jonas Borgström to daniel

comment:14 Changed 11 years ago by Matthew Good

Component: projectgeneral
Owner: changed from daniel to Jonas Borgström

comment:15 Changed 11 years ago by Gunnar Wagenknecht <gunnar@…>

Cc: gunnar@… added

comment:16 Changed 11 years ago by anonymous

I think project summary (WikiStart) should contain "news" or "announce". To enable this, add the new type named "news" or "announce" to ticket by default, and show recent of these summaries by macro.

And I think "recent colosed tickets", "recent added tickets", and these kind of information can be showed using some macro by defaults.

comment:17 Changed 11 years ago by Tov Are

Cc: gunnar@… removed

Tidsstyring

Jeg savner muligens mulighet til å legge inn tidsestimater på tickets. Det ville vere nyttig, å kunne ha den type informasjon i samme systemet.

comment:18 Changed 11 years ago by Tov Are

Cc: gunnar@… added

comment:19 Changed 10 years ago by anonymous

Owner: changed from Jonas Borgström to me
Priority: normallowest
Severity: normalminor
Version: 0.6.10.9

comment:20 Changed 10 years ago by Emmanuel Blot

Milestone: 1.0
Owner: changed from me to Jonas Borgström
Priority: lowestnormal
Severity: minornormal
Version: 0.90.6.1

comment:21 Changed 10 years ago by Christian Boos

Milestone: 1.0

According to our roadmap, this should be a 1.0 feature.

comment:22 Changed 10 years ago by Christian Boos

Keywords: project added
Severity: normalmajor

comment:23 Changed 10 years ago by anonymous

Priority: normalhighest

comment:24 Changed 10 years ago by Matthew Good

Priority: highestnormal

comment:34 Changed 10 years ago by anonymous

Cc: gunnar@… removed

comment:35 Changed 10 years ago by anonymous

Resolution: fixed
Status: newclosed

comment:36 Changed 10 years ago by Christian Boos

Resolution: fixed
Status: closedreopened

Quite unbelievably, this is not a test ticket, but a valid one.

Though the question of whether this should be done as a plugin might be asked…

An alternative to a plugin would be the possibility to have macros that can provide all the required info an be inserted in the WikiStart page.

e.g. the TicketQuery macro could be adapted to accept a count format, in addition to the compact one, and that would simply show the number of tickets matching the specific request.

  • trac/ticket/query.py

     
    677677    This macro accepts two parameters, the second of which is optional.
    678678
    679679    The first parameter is the query itself, and uses the same syntax as for
    680     {{{query:}}} wiki links. The second parameter determines how the list of
    681     tickets is presented: the default presentation is to list the ticket ID next
    682     to the summary, with each ticket on a separate line. If the second parameter
    683     is given and set to '''compact''' then the tickets are presented as a
    684     comma-separated list of ticket IDs.
     680    {{{query:}}} wiki links.
     681
     682    The second parameter determines how the list of tickets is
     683    presented: the default presentation is to list the ticket ID next
     684    to the summary, with each ticket on a separate line.
     685    If the second parameter is given, it must be one of:
     686     - '''compact''' -- the tickets are presented as a comma-separated
     687       list of ticket IDs.
     688     - '''count''' -- only the count of matching tickets is displayed
    685689    """
    686690
    687691    def render_macro(self, req, name, content):
    688692        query_string = ''
    689         compact = 0
     693        compact = False
     694        count = False
    690695        argv = content.split(',')
    691696        if len(argv) > 0:
    692697            query_string = argv[0]
    693698            if len(argv) > 1:
    694                 if argv[1].strip().lower() == 'compact':
    695                     compact = 1
     699                format = argv[1].strip().lower()
     700                if format == 'compact':
     701                    compact = True
     702                elif format == 'count':
     703                    count = True
    696704
    697705        buf = StringIO()
    698706
     
    709717                        (ticket['status'], href, summary, ticket['id'])
    710718                    links.append(a)
    711719                buf.write(', '.join(links))
     720            elif count:
     721                buf.write(len(tickets))
    712722            else:
    713723                buf.write('<dl class="wiki compact">')
    714724                for ticket in tickets:

comment:37 Changed 10 years ago by Christian Boos

btw, the count format is now implemented in 0.11.

comment:38 Changed 10 years ago by Christian Boos

Description: modified (diff)
Owner: changed from Jonas Borgström to Christian Boos
Priority: normalhigh
Severity: majorcritical
Status: reopenednew
Summary: Add a new project summary module. (My Page)Add a new project summary module.

I've removed (My Page) from the summary, as this is more related to #4588.

This is about whole project summary, which makes a lot of sense in the multiple project per environment case.

See TracMultipleProjects/SingleEnvironment#Projectresource.

comment:39 Changed 10 years ago by Christian Boos

#1877 proposed a patch on 0.8 to give a summary of tickets for all projects (in the multiple environment case).

This makes me think that in order to complement the Project Summary, there should probably be a Projects Overview, in the same vein as we now have a Milestone and the Roadmap for getting an overview of all the milestones.

comment:40 Changed 8 years ago by a.a.vykhodtsev@…

Cc: a.a.vykhodtsev@… added

comment:41 Changed 7 years ago by Thijs Triemstra <lists@…>

Cc: lists@… added

comment:42 Changed 7 years ago by lkraav <leho@…>

cool, first ticket ever.

from the looks of the description, it would seem the current 0.12-trunk capabilities of Roadmap fulfill the original idea.

or what's the latest thought process on this for you cboos?

comment:43 Changed 6 years ago by Christian Boos

Milestone: 1.0unscheduled

Milestone 1.0 deleted

comment:44 Changed 6 years ago by Christian Boos

Milestone: triaging0.13

Complementary to #130 / #11025.

The exact form this could take should be very free form, so perhaps rather than the fixed model followed by a milestone (description + ticket progress bar), a project overview could be generated from a set of macros that could be freely modified and repositioned in the project's description. The default layout and content could be taken from ProjectTemplates? sub-pages, with a nice ProjectTemplates?/default.

Last edited 4 years ago by Christian Boos (previous) (diff)

comment:45 Changed 6 years ago by Christian Boos

Keywords: multiproject added; project removed

comment:46 Changed 6 years ago by Carsten Klein <carsten.klein@…>

Perhaps this could be made a DashboardPlugin? where the user can edit the page layout and define what is shown and what is not on the DashboardPlugin? admin page.

The dashboard plugin itself should provide extension points, for example DashboardInformationProvider? which can then be implemented by for example the ticket system, for example the LatestTicketChangesInformationProvider?, or the MostActiveTicketsInformationProvider? and so on.

On the admin page then, the user can opt in/out individual such information providers, setting them up in for example a two or three column layout.

On the dashboard page itself, the user might be enabled to drag around individual renderings of the available information providers to their personal likings, collapsing or expanding individual such renderings.

In a multi project scenario, the multi project system would then provide new implementations of these information providers, overriding the defaults in the system provided by the ticket system, the timeline and so on, coalescing the information from these multiple projects into a single view.

comment:47 in reply to:  18 Changed 6 years ago by Carsten Klein <carsten.klein@…>

Replying to anonymous:

I think project summary (WikiStart) should contain "news" or "announce". To enable this, add the new type named "news" or "announce" to ticket by default, and show recent of these summaries by macro.

And I think "recent colosed tickets", "recent added tickets", and these kind of information can be showed using some macro by defaults.

I do not think that the original WikiStart page should be replaced by something like the dashboard.

If you want to include such information on your WikiStart page, your best bet is to implement or use an existing macro and use that on your page.

-10 for replacing the WikiStart by a Dashboard from me.

comment:48 in reply to:  46 Changed 6 years ago by Carsten Klein <carsten.klein@…>

Replying to Carsten Klein <carsten.klein@…>:

Perhaps this could be made a DashboardPlugin? where the user can edit the page layout and define what is shown and what is not on the DashboardPlugin? admin page.

with that I meant that the plugin will provide a requesthandler responsible for the /dashboard realm.

comment:49 Changed 6 years ago by Ryan Ollos <ryano@…>

Cc: ryano@… added

comment:50 Changed 6 years ago by Itamar Ostricher

Cc: itamarost@… added

comment:51 Changed 6 years ago by tn@…

Cc: tn@… added

comment:52 in reply to:  51 Changed 6 years ago by anonymous

Replying to tn@…:

(<snip> some spam)

Last edited 6 years ago by Christian Boos (previous) (diff)

comment:53 Changed 6 years ago by Christian Boos

SpamFilter said:

CaptchaSystem (10): Human verified via CAPTCHA

Either there's a bug in the SpamFilter, or that was really a real human behing the keyboard… @anonymous, would you mind confirming?

comment:54 Changed 6 years ago by Dirk Stöcker

Have a look at the apache server and trac logs. They should tell you whether the captcha was solved or not :-)

comment:55 Changed 6 years ago by Christian Boos

Milestone: 0.130.14-multiproject

comment:56 Changed 4 years ago by lkraav <leho@…>

Cc: leho@… added

Not sure why I commented but didn't cc before. Anyway, Bloodhound is shipping their alpha preview 0.1 release with a Dashboard view. That should be interesting to look at.

comment:57 Changed 2 years ago by Ryan J Ollos

Cc: Ryan J Ollos added; ryano@… removed

comment:58 Changed 16 months ago by Ryan J Ollos

Owner: Christian Boos deleted

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned. Next status will be 'new'.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.