#12031 closed enhancement (fixed)
Allow for multiple projects to have the same milestones
Reported by: | Owned by: | Cinc-th | |
---|---|---|---|
Priority: | normal | Component: | SimpleMultiProjectPlugin |
Severity: | normal | Keywords: | |
Cc: | Trac Release: |
Description
I tried assigning the same milestone to multiple projects, which basically have the same roadmap. This failed, of course, but it would be nice if that was possible.
For example, it is not possible to have a milestone named "alpha" for two different projects.
Attachments (0)
Change History (23)
comment:1 Changed 10 years ago by
comment:2 Changed 10 years ago by
Owner: | changed from falkb to Cinc-th |
---|---|
Status: | new → accepted |
comment:4 Changed 10 years ago by
Summary: | Allow for multiple projects to have the same milestones → Allow for multiple projects to have the same milestones or versions |
---|
comment:7 follow-ups: 8 10 Changed 10 years ago by
I'm looking for Model::get_milestones_for_projectid(). What is the new API function for it?
comment:8 follow-up: 12 Changed 10 years ago by
Replying to falkb:
I'm looking for Model::get_milestones_for_projectid(). What is the new API function for it?
There is currently no such thing. I just implemented the methods I needed while doing other stuff.
Doing a fast scan I found the old model doesn't have something like that either. Having said that I believe the method you are looking for is a worthwhile addition. I may manage to put something together today or tomorrow.
comment:9 Changed 10 years ago by
Status update:
- Association of multiple projects with milestones and versions is implemented.
- Roadmap handling needs a massive make over so milestones are properly displayed
I found that the roadmap plugins in SMP are intertwined with the version plugin. This means that you must activate the version plugin to have a proper SMP roadmap.
I intend to separate the functionality so you may for example disable the version stuff without breaking the roadmap. This could mean we have for some time a feature regression while the new roadmap is implemented. To prevent such a regression one had to do the makeover locally and apply everything in a huge changeset. I'm not sure that is feasible.
While implementing a new roadmap #10087 may be fixed too.
comment:10 follow-up: 11 Changed 10 years ago by
Replying to falkb:
I'm looking for Model::get_milestones_for_projectid(). What is the new API function for it?
New in [14663]:
SmpComponent::get_components_for_project_id()
SmpMilestone::get_milestones_for_project_id()
SmpVersion::get_versions_for_project_id()
All methods return a (possibly empty) list of names.
comment:11 Changed 10 years ago by
Replying to Cinc-th:
Replying to falkb:
I'm looking for Model::get_milestones_for_projectid(). What is the new API function for it?
New in [14663]:
SmpComponent::get_components_for_project_id()
Yeah, this is great, works well here (I have another plugin using those functions). Thanks a lot!
I've successfully updated to [14664], and didn't notice any trouble at the first glance, though I didn't try to link a milestone/version to more than one project. Great that the space below the filter-box is used by the project boxes now!!
comment:12 Changed 10 years ago by
comment:13 Changed 10 years ago by
Another question: Could you support a setting which restricts to only 1 project per milestone/version? Here, we need this restriction. :)
comment:15 Changed 9 years ago by
comment:22 Changed 9 years ago by
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
Summary: | Allow for multiple projects to have the same milestones or versions → Allow for multiple projects to have the same milestones |
Narrowing this ticket to milestones only.
A follow up ticket for tracking progress for multiple projects for versions has been created: #12557
In 14645: