Ticket #10813 (closed defect: invalid)

Opened 4 months ago

Last modified 4 months ago

Existing Versions are not accessible - should versions span across projects

Reported by: hilligom@gmail.com Assigned to: falkb
Priority: normal Component: SimpleMultiProjectPlugin
Severity: normal Keywords:
Cc: Trac Release: 0.12

Description

I installed the plugin and everything worked but the Version field in new tickets only listed the default version listed in the .ini file. If I tried creating specific versions inside a project that had already been defined it gave me an error.

I am wondering if custom versions for projects could be optional. Imagine I want to manage 3 projects separately but they all end up getting released in the same version of an application. I would have to define the same version 3 times instead of working from a global list.

Attachments

Change History

(follow-up: ↓ 2 ) 01/22/13 08:43:08 changed by falkb

  • owner changed from crossroad to falkb.
  • status changed from new to assigned.

There is no support for global ressources 'version' or 'milestone' shared by more than one project. Per definition, this plugin only supports one project for a certain version, and one project for a certain milestone. When creating or modifying versions and milestones on the Roadmap page you must assign them to one of your projects. After that you'll get those versions and milestones as choice in the appropriate dropboxes on your 'New Ticket' page.

Your described situation looks like you're missing the assignment of your version to the project you selected in the 'New Ticket' form. Go to page 'Roadmap', edit your desired version by 'Change version' button, and assign its project to it. Then try 'New Ticket' again.

(in reply to: ↑ 1 ) 01/22/13 14:02:34 changed by hilligom@gmail.com

Replying to falkb:

There is no support for global ressources 'version' or 'milestone' shared by more than one project. Per definition, this plugin only supports one project for a certain version, and one project for a certain milestone. When creating or modifying versions and milestones on the Roadmap page you must assign them to one of your projects. After that you'll get those versions and milestones as choice in the appropriate dropboxes on your 'New Ticket' page. Your described situation looks like you're missing the assignment of your version to the project you selected in the 'New Ticket' form. Go to page 'Roadmap', edit your desired version by 'Change version' button, and assign its project to it. Then try 'New Ticket' again.

I don't have a change version button available only Add New Milestone and Add New Version.

(follow-up: ↓ 4 ) 01/22/13 14:07:06 changed by falkb

Does your Roadmap page display versions? Probably switch on the checkbox "Show completed milestones or versions".

If yes, enter such version on the Roadmap page and look for the "Edit" button at the bottom of that page. Does this work for you?

(in reply to: ↑ 3 ) 01/22/13 14:10:11 changed by anonymous

  • status changed from assigned to closed.
  • resolution set to invalid.

Replying to falkb:

Does your Roadmap page display versions? Probably switch on the checkbox "Show completed milestones or versions". If yes, enter such version on the Roadmap page and look for the "Edit" button at the bottom of that page. Does this work for you?

This worked. Thank you!

(follow-up: ↓ 6 ) 01/22/13 14:11:11 changed by falkb

Is your problem solved now?

(in reply to: ↑ 5 ) 01/22/13 14:18:51 changed by anonymous

Replying to falkb:

Is your problem solved now?

The plugin seems to be working as expected. We still need to use versions across different projects so for now I have turned off SmpTicketProject? so that my global versions are still accessible in new tickets. We may need to look at changing our workflow of tickets before using the full features of the plugin going forward. Thanks again for the quick response!

01/22/13 14:36:13 changed by falkb

Wiki page T:TracMultipleProjects/SingleEnvironment mentions "What about Global or Shared Resources?" as open question.

Well, I also have several projects containing e.g. version v1.0, though they have different release dates. I solved that problem by adding a prefix to each version string, for instance "project 1 - v1.0" and "project 2 - v1.0", you know it's just a label. This way I never needed to share one version by multiple projects.

Do you just need to reuse that version label, or is it also one and the same release package, or event respectively, for your different projects?

01/22/13 14:42:26 changed by anonymous

Right now all new production defects come in with a version of "review" for our support team to triage from there they will be moved to the appropriate project/milestone.

Project wise we open tickets directly under the correct project/milestone so version isn't as big a deal here.

Tonight I will turn the SmpTicketProject? back on and try a few more things. Ultimately we may just need to add a new field or status to assist in triaging production issues.

01/22/13 14:52:32 changed by falkb

Yes, this very much sounds rather like a new custom ticket field, probably a checkbox "production issue", or simply use a predefined value for the keywords ticket field. The use of 'version' seems to be a bit inappropriate.

Add/Change #10813 (Existing Versions are not accessible - should versions span across projects)




Change Properties
Action