Edgewall Software
Modify

Opened 10 years ago

Last modified 5 years ago

#11919 new enhancement

Make diff paths available in the UI.

Reported by: wrinkledcheese@… Owned by:
Priority: normal Milestone: next-major-releases
Component: web frontend Version: 1.0.1
Severity: normal Keywords:
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description

In regards to this ticket:

http://trac.edgewall.org/ticket/9824

If I want to compare a branch vs trunk. Eg Observing a junior/new hire's work. I have to go into the HTML - using a DOM inspector - and manually change the "old path" hidden form field to trunk.

This could easily be made available in the interface for users. It would also make my life easier.

I could probably contribute this change if it is seen as a valuable enhancement by others.

When comparing trunk(old path) against a branch(new path) the revision must be set to the latest revision of the branch.

Attachments (0)

Change History (7)

comment:1 by Ryan J Ollos, 10 years ago

Sounds reasonable. I've felt that the diff module was not visible enough. I used Trac for years before discovering it. What if we just linked to the diff page and populated some of the inputs? For example, if you are on branches/0.11-stable where the HEAD revision is [10236], we could have a link that jumps to diff (/diff?new_path=%2Fbranches%2F&new=10236).

Last edited 10 years ago by Ryan J Ollos (previous) (diff)

comment:2 by Jun Omae, 10 years ago

We could use "View changes…" button at the bottom of browser view to compare two branches. Clicking button shows the diff page with branch and revision in the browser view.

Last edited 10 years ago by Jun Omae (previous) (diff)

comment:3 by Ryan J Ollos, 10 years ago

For years I didn't know about the View changes… button and even forgot about it again while writing my comment. It feels misplaced, in a location that content modification buttons are usually positioned. Perhaps it would be better located near the #diffrev, or in the contextual navigation.

comment:4 by Ryan J Ollos, 10 years ago

Milestone: next-dev-1.1.x

Keeping ticket open to consider relocating the View changes… button.

comment:5 by Ryan J Ollos, 9 years ago

Milestone: next-dev-1.1.xnext-dev-1.3.x

Narrowing focus for milestone:1.2. Please move ticket to milestone:1.2 if you intend to fix it.

comment:6 by Ryan J Ollos, 5 years ago

Milestone: next-dev-1.3.xnext-dev-1.5.x

Milestone renamed

comment:7 by Ryan J Ollos, 5 years ago

Milestone: next-dev-1.5.xnext-major-releases

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned.
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.