Edgewall Software
Modify

Opened 5 years ago

Last modified 5 years ago

#13201 new enhancement

URL parameter defaults for milestone forms

Reported by: anonymous Owned by:
Priority: normal Milestone: next-major-releases
Component: general Version:
Severity: normal Keywords:
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description

Ticket and wiki form defaults can be controlled by URL parameters:

The same would be useful for milestones:

But the default values are ignored there.

Attachments (0)

Change History (10)

comment:1 by Ryan J Ollos, 5 years ago

Milestone: next-major-releases

comment:2 by anonymous, 5 years ago

I just noticed /milestone?action=new exists, and there /milestone?action=new&name=MyDefaultValue works. Great!

So /admin/ticket/milestones?name=MyDefaultValue is not urgently needed.

Unfortunately I think the other field default values like due checkbox or description can not be controlled here either.

comment:3 by Jun Omae, 5 years ago

-1. That behavior doesn't sound secure. I think we should let the administrators explicitly enter the form in administrative pages.

comment:4 by Ryan J Ollos, 5 years ago

What is the use-case for specifying milestone fields from a link? Name must be unique, so it can only be used once. The only other fields are Due, Completed and Description; which are usually unique.

I don't see a use-case like with tickets where you might want to have the Component, Type or a custom field set when creating a certain category of ticket.

comment:5 by anonymous, 5 years ago

The use-case is semi-automated release process. Consider make release to (among many other steps) open in browser:

  • /milestone?action=new&name=2019-10&due=1month
  • /milestone/2019-09?action=edit&completed=today&retarget=2019-10&description=See%20wiki:Downloads/2019-09

So these can easily be submitted, maybe with optional minor manual adjustments.

comment:6 by anonymous, 5 years ago

I don't understand security problem. Ticket and wiki forms and milestone name already have this feature.

Forget about admin page if that is the problem. Consider only /milestone page for action=new and action=edit please.

in reply to:  5 comment:7 by Ryan J Ollos, 5 years ago

Replying to anonymous:

The use-case is semi-automated release process. Consider make release to (among many other steps) open in browser:

That's the intended use of TracAdmin:

$ trac-admin ../tracenvs/proj-1.3 help milestone add
milestone add <name> [due]

    Add milestone

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

comment:8 by anonymous, 5 years ago

Trac-admin does not work without remote access which is a big can of worms.

comment:9 by Ryan J Ollos, 5 years ago

XmlRpcPlugin can be used to create milestones remotely.

comment:10 by anonymous, 5 years ago

Thanks for the suggestion. We prefer the semi-interactive process using /milestone?action=new&name=2019-10 for confirmation purposes and optional minor manual adjustments. The only downside we see is that for some fields a default value can not yet be set.

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.