Last modified: 2014-02-28 13:52:31 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 26416 - Ability to view the revision follow-up tree
Ability to view the revision follow-up tree
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
CodeReview (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on: 29916
Blocks: noncoreapi
  Show dependency treegraph
 
Reported: 2010-12-24 16:06 UTC by Happy-melon
Modified: 2014-02-28 13:52 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Happy-melon 2010-12-24 16:06:49 UTC
CR groups revisions into 'trees' based on the commit summary: the revision is assumed to be a follow-up to any revisions named in the summary, and follow-up revisions are listed below the diff on the original commit.  But users can make typos, forget to mention the previous commit, or otherwise fail to build a proper tree.  And in fact you can't really *see* the full tree structure anywhere, only the immediate parent/child relations.  

It would be preferable if the full tree structure for at least a couple of levels either side was visible below the diff, and that there was a way to edit the structure, either in-place or via a separate page.
Comment 1 Roan Kattouw 2010-12-29 14:07:49 UTC
The structure is already editable in trunk, see bug 25638. Being able to view the full tree structure (not just first-level follow-ups to a rev, but nth-level follow-ups and predecessors as well) would also be useful, yes.
Comment 2 Sam Reed (reedy) 2010-12-31 04:59:51 UTC
Do you want a list of what this rev links to in it's summary (predecessors) (and any manually referenced), followups to it's followups in the table (or similar) at the bottom?
Comment 3 Roan Kattouw 2010-12-31 14:29:53 UTC
(In reply to comment #2)
> Do you want a list of what this rev links to in it's summary (predecessors)
> (and any manually referenced), followups to it's followups in the table (or
> similar) at the bottom?
A more graphical "tree" would be cool, but a predecessor list and an infinite-depth follow-up list would be useful already.
Comment 4 Niklas Laxström 2010-12-31 14:34:36 UTC
How about an API module first? Maybe someone wants to innovate with the data...
Comment 5 Sam Reed (reedy) 2010-12-31 15:15:56 UTC
(In reply to comment #4)
> How about an API module first? Maybe someone wants to innovate with the data...

I was just thinking the same. It's certainly something that could be done better ajaxy
Comment 6 Sam Reed (reedy) 2011-03-04 23:58:44 UTC
Just thinking what we need in the API module (or adding to)...

A list of all followup revisions? Maybe with some basic information?
Comment 7 Sam Reed (reedy) 2011-05-22 20:44:37 UTC
Ping?
Comment 8 Sam Reed (reedy) 2011-09-06 11:33:29 UTC
(In reply to comment #6)
> Just thinking what we need in the API module (or adding to)...
> 
> A list of all followup revisions? Maybe with some basic information?

Done for bug 29916 in r96321, displays same info as we get at the bottom of the CR display pages

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


Navigation
Links