Redmine OCIO y TECnología: Issueshttps://redmine.ociotec.com/https://redmine.ociotec.com/favicon.ico?15768443862023-04-07T20:06:25ZRedmine OCIO y TECnología
Redmine Ads - Feature #1615 (In progress): Redmine 5 supporthttps://redmine.ociotec.com/issues/16152023-04-07T20:06:25ZEmilio González MontañaAdvanced roadmap - Feature #1614 (Resolved): Redmine 5 supporthttps://redmine.ociotec.com/issues/16142023-04-07T19:58:20ZEmilio González MontañaLocalizable - Feature #1613 (Resolved): Redmine 5 compatibilityhttps://redmine.ociotec.com/issues/16132023-04-04T20:58:17ZEmilio González MontañaTime report - Feature #1586 (Resolved): Generate first version of the plugin with Redmine 4 supporthttps://redmine.ociotec.com/issues/15862020-06-14T21:22:07ZEmilio González MontañaAdvanced roadmap - Feature #1565 (Resolved): Redmine 4 supporthttps://redmine.ociotec.com/issues/15652019-12-31T18:51:53ZEmilio González MontañaAds - Feature #1462 (Resolved): Custom HTML blockhttps://redmine.ociotec.com/issues/14622017-09-28T23:30:23ZEmilio González MontañaAds - Feature #1424 (Resolved): Add permissions to render adshttps://redmine.ociotec.com/issues/14242017-08-19T10:50:09ZEmilio González MontañaAds - Feature #1394 (Resolved): Adapt to Redmine 3.4.x changeshttps://redmine.ociotec.com/issues/13942017-07-28T23:09:04ZEmilio González MontañaData - Feature #1377 (Resolved): Crete empty plugin skeletonhttps://redmine.ociotec.com/issues/13772017-05-28T12:37:48ZEmilio González MontañaAds - Feature #1376 (Resolved): Add setting for Google ad block titlehttps://redmine.ociotec.com/issues/13762017-05-27T18:48:25ZEmilio González MontañaAds - Feature #1375 (Resolved): Add setting for Patreon tittlehttps://redmine.ociotec.com/issues/13752017-05-27T18:45:51ZEmilio González Montaña
<ul>
<li>Reuse Patreon on mouse over text setting.</li>
<li>Show tittle above Patreon logon if setting is not empty.</li>
<li>Show predefined label for mouse over text.</li>
</ul> Ads - Feature #1370 (Resolved): Allow custom header code insertionhttps://redmine.ociotec.com/issues/13702017-04-27T10:24:09ZEmilio González MontañaAdvanced roadmap - Feature #1340 (New): Milestone and Versions orderinghttps://redmine.ociotec.com/issues/13402017-04-09T04:21:51ZArtur H
<p>It would be extremely useful to manually order versions and milestone.</p>
<p>We do not set due-date for versions and milestones (ideally, these would be automatically calculated by the advanced roadmap plugin), instead we would like to be able to specify order in which versions are being completed.</p> Advanced roadmap - Feature #1325 (New): Assign tickets to Milestonehttps://redmine.ociotec.com/issues/13252017-03-29T07:13:55ZArtur H
<p>I would like to use Milestone for Release planning. So it would be very useful to be able to assign tickets to a Milestone.</p>
The way I see it working is:
<ol>
<li>I plan for next big product release which involves a few Redmine projects</li>
<li>I create a new Milestone for that (I call it Release) and create a set of "Features" for the release.</li>
<li>Now I create new version for each project involved and assign it to the Milestone</li>
<li>Now, within a project version I create subticket of Milestone features for implementing this feature within this project version</li>
<li>Then we could have a Spring in each project for a feature implementation.</li>
</ol>
<p>Do you think it makes sense?</p> Advanced roadmap - Feature #1324 (Resolved): Estimated due date for Milestonehttps://redmine.ociotec.com/issues/13242017-03-29T07:08:57ZArtur H
Due in and Due in (estimated speed) are very nice. However, I would like it to be extended with a little more functionality:
<ol>
<li>Estimated completion date - calculated date when the Milestone will be completed. It should take into account only workdays (omit weekends from calculation). Also for the Estimated due-date it could use configurable workload. So, let's say we know we can only dedicate 50% of resources to the project, so 8h of work would be done in 2 days. So, it would be very useful to have calculated completion date with all the constraints.</li>
<li>Estimated completion date (estimated speed) as above, but instead of using configured workload, use the calculated speed for estimation completion date. And of course omit weekends from the calculation.</li>
</ol>