Edgewall Software
Modify

Opened 13 years ago

Closed 3 years ago

Last modified 3 years ago

#3776 closed enhancement (fixed)

wiki-behaviour of roadmap pages

Reported by: pim@… Owned by: Ryan J Ollos
Priority: high Milestone: 1.3.2
Component: roadmap Version: 0.9.6
Severity: normal Keywords: tracobject
Cc: trac@…, leho@…, Ryan J Ollos Branch:
Release Notes:

Added autopreviews to all textareas that accept wiki markup.

API Changes:

Description

Hi,

We make extensive use of the Roadmap for tracking of current todos, subprojects and information about the functionality and even time-tracking (that might be another nice feature) but we really dislike the fact that changes to roadmap pages are not visible in the recent activity tab, neither do the roadmap pages have a wiki-like history with rollback functionality.

It would be great if Roadmap pages would behave themselves as normal wiki pages.

Thanks!

Pim Rupert - pim@…

Attachments (0)

Change History (26)

comment:1 by Christian Boos, 13 years ago

Keywords: tracobject added
Milestone: 1.0
Owner: changed from Christopher Lenz to Christian Boos

"Roadmap pages", i.e. Milestone resources, could of course benefit of the same functionality than Wiki pages, but first a more unified data model is needed for that (see TracObjectModelProposal).

comment:2 by Emmanuel Blot, 13 years ago

As 1.0 is about a 2-year timeframe, I think it would be nice to implement a preview feature for editing milestone info. It would not keep the history of previous editions, nor be a Timeline event provider, but the interface would be more consistent with the existing editable items (wiki page, ticket).

comment:3 by Christian Boos, 13 years ago

… on the other hand, as currently changes are costless and not versioned, Save works like a preview ;)

comment:4 by Emmanuel Blot, 13 years ago

Save does not work like a preview.

We use a lot of milestones in our project, and each milestone page contains a lot of info, which usually means that the page needs to be reworked several times before being valid (escaping camel case syntax, mostly).

When you click on Save, you got the final page: it is not possible to have the edit box and the rendered text:

  1. Go to the bottom of the page
  2. Select 'Edit' again, which reloads the page
  3. Edit the wiki text
  4. Select 'Save', to render the page content

This is far from being as convenient as a real preview feature that shows both the edit area and the rendered page. The edit workflow is quite different that the one for a wiki page.

comment:5 by Christian Boos, 13 years ago

#4569 also requested the ability to be able to at least preview Milestone description changes.

As soon as the current changes are finalized, I'll start on the GenericTrac proposal with the milestone as the first example.

comment:6 by trac@…, 13 years ago

Cc: trac@… added

comment:7 by Christian Boos, 12 years ago

#6462 was closed as duplicate.

comment:8 by Ryan Ollos <ryano@…>, 10 years ago

Cc: ryano@… added

comment:9 by Christian Boos, 10 years ago

#1673 was about a subset of the features implied by this ticket (milestone history).

comment:10 by lkraav <leho@…>, 10 years ago

Cc: leho@… added

comment:11 by Christian Boos, 10 years ago

Milestone: 1.0unscheduled

Milestone 1.0 deleted

comment:12 by Christian Boos, 9 years ago

Milestone: triagingnext-major-0.1X
Priority: normalhigh

comment:13 by trac@…, 8 years ago

This has led to confusion in a number of software projects where I chose trac as the PM tool. People do not understand why everything in trac is about versioned documents but the description of milestones. It's of particular importance if you keep feature lists in the milestone description that everybody agreed upon, and suddenly find that somebody has changed them.

comment:15 by Ryan J Ollos, 5 years ago

Cc: Ryan J Ollos added; ryano@… removed

comment:16 by Ryan J Ollos, 5 years ago

Owner: Christian Boos removed

comment:17 by Peter Suter, 3 years ago

#10807 was closed as a duplicate.

#1113 is also related.

comment:18 by Ryan J Ollos, 3 years ago

It would be simple enough to add autopreview capability to the Milestone edit and several other views. This would be a progressive enhancement and given the additional work required I don't see it as necessary to have an explicit Preview that reloads the page.

Possible targets for auto preview:

  • Report description
  • Milestone description
  • Admin milestone description
  • Admin component description
  • Admin version description
  • Admin repository description

Is it a good JavaScript pattern to have showOnPreview return the callback?

log:rjollos.git:t3776_autopreviews.

comment:19 by Ryan J Ollos, 3 years ago

Milestone: next-major-releases1.3.2
Owner: set to Ryan J Ollos
Status: newassigned

comment:20 by Ryan J Ollos, 3 years ago

Release Notes: modified (diff)

comment:21 by Ryan J Ollos, 3 years ago

Fixed some issues and added autopreview for all textareas [4a1ba19d/rjollos.git].

comment:22 by Ryan J Ollos, 3 years ago

admin.css was modifying the wiki autopreview, fixed in [380cb731/rjollos.git]. Rebased branch: log:rjollos.git:t3776_autopreviews.2.

comment:23 by Ryan J Ollos, 3 years ago

Resolution: fixed
Status: assignedclosed

Committed to trunk in r15844.

comment:24 by Ryan J Ollos, 3 years ago

Described in comment:11:ticket:11649, we need escape inputs using to_json or to_javascript. Proposed changes in [d6aa9175d/rjollos.git]. I'll commit to 1.2-stable, as applicable (e.g. wiki_edit.html).

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

comment:25 by Ryan J Ollos, 3 years ago

comment:24 changes committed to 1.2-stable in r15941, committed to trunk in r15942.

comment:26 by Jun Omae, 3 years ago

I think we should backport r15941 to 1.0-stable. 1.0-stable has the same issue.

comment:27 by Ryan J Ollos, 3 years ago

Okay, backported to 1.0-stable in r15948.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Ryan J Ollos.
The resolution will be deleted. Next status will be 'reopened'.
to as closed The owner will be changed from Ryan J Ollos to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.