Computing Projects Improvements

A list (in no order) of known bugs and suggested enhancements to the Computing Projects framework or its technical implementation.

ToDo List

  1. When calculating the standard deliverables, the DB doesn't ignore any specific deliverables that have been abandoned.
  2. "I added a comment to https://computing.projects.inf.ed.ac.uk/waiting/#315 - but that new comment was then added to a previous old comment by me, leading both to the loss of the original timestamp, and a somewhat garbled single final statement. That doesn't sound like the correct behaviour."
  3. Change m81/m82 messages to go out on Friday for previous week as that will bebetter reflect submissions and be more in advance of CEG
  4. Sort out "actions" so they are shown on projects pages and master index page - anyone can change (link from agenda)
  5. Add "completed" and "approved" pendings to oversight message - make it more of an action agenda where oversight bit at present is one section
  6. Rating value change graph added to projects pages
  7. Better visualisation of due/overdue submission/committment - colorised rows, extra indicator fields - can also just use a query to restrict rows to get most of the way: "It would be nice if the fields which were overdue could be highlighted in some way; and ones which were imminent also highlighted, but differently.", "Yes, that would be very nice. It is related to the generic functionality identified as an enhancement in Trac#455 and that ones been there for 5 years so ... You could probably use some specific queries to help reduce data clutter but that might be more trouble than you want."
  8. "The "effort" and "owner" pages seem to be summarily chopped at the bottom." - "Hmm - whats your display resolution, try using browser to zoom out the page? Full dynamic resizing is another enhancement ticket somewhere ..."
  9. Committment reminder could include stats (accrued etc)?
  10. Project per-person admin pages - also for all staff e.g. status of requested projects, talks done, overall effort and committment, etc
  11. Add overall "activity rating" for project on web pages - this is its own rating percent of activity vs committment from incept, or is it also still relative to others - anyway its not the weekly rating used to set position. probably mapped to a simple high/medium/low indicator on main page
  12. more post-review checks, e.g. justification statement set; also on desktop for base query so projects don't go as as soon as status changed
  13. Craig and Alastair seem to be being dealt a somewhat unfair hand in review allocation - they have shared the last nine reviews between them. Not quite sure why, will need to look again at the function doing random selection - it seemed to work perfectly fine in isolation and prior to the last nine the randomness seemed more reasonable so I am guessing something changed a little while ago to affect it. Will investigate. The most recent review went to me though so ... who knows. This SQL biases results based on previous reviews - tending towards same for all not sure if quite right or could be simplified: with i as ( select random() as i ), r as ( select reviewer r, count() n from project group by reviewer ), xr as ( select r, n, sum(n) over (order by n) as t from r group by r, n ), nxr as ( select i.i, xr., sum(t) over () - t as nt from xr, i ), nnxr as ( select *, nt / sum(nt) over () * 100 as x from nxr ) select r from nnxr where i * 100 > x order by x desc limit 1; In principle seems to work but not implemented in feed yet
  14. have a "lightweight" settable by checkbox on submission (probably only visible if CO) (but also in review). such a project can be self-reviewed as-is and automatically approved and has fewer default targets. Use for projects less than a week maybe and no side-effects, make it easier for misc-development to be published. No mandated talk, no mandated blogging, etc. probably a homepage though. obviously can take priority over another non-lightweight project with impending deadlines etc - shown on web pages at bottom, grey, and with no activity rating report
  15. re. pending/wishlist - this is an additional checkbox on request form (COs only), like lightweight skips some process (e.g. no immediate review just goes into "holding")
  16. deliverable "pending"+date, presented as "Intention to Meet by DATE: commment"
  17. TP218 sometimes fails - in one instance due to # in the "reason" field. Make more robust.
  18. project stats accrued ranking do not seem to work even after one week in ..., may be due to when submit/commit records created, e.g. if no commit record (see 25) ?
  19. can't add talks that aren't associated with an actual project - need to be able to add talks against accounts (e.g. computing team) when not specific - same for actions, i.e. we need to include in the drop-down some variants of pseudo projects
  20. include the priority+justification details on the "approval check" email
  21. report deadlines within the upcoming committment period at the start of that period, perhaps with committment request, but also in weekly CEG report
  22. Projects need at least one specific deliverable to show up on the "Owner" panel however if not added at Review stage then this can't be done via desktops. This is a desktop bug, it needs to be a join local restriction on each deliverable box but isn't at the moment. - drop requirement for review to require a specific deliverable
  23. Consider relabeling target priorities so more obvious usage:
    • (15:24:12) ascobie: I'll write M -> S -> O on my whiteboard to remind me
    • (15:25:42) timc/work: hmm ok will have a look, maybe we should relabel eg, M (High), S (Medium), O (Low) or something like that, will add to the list
  24. move report stat calculations and message triggers into views (and/or coupler derived)
  25. validate effort figure resolution (non-null, although conflicts with some effort types, could use a default)
  26. early query maybe now redundant or just needing docs: On which page should I be setting project deadlines? If I try it on the "(Edit) Owner" page it won't let me change the date in the deliverables column?
  27. The approval detection is clearly a bit primitive as it just trusts the status value. Neither of these projects have a justification statement or deliverable. To add these you will need to get them back into the Reviewer panel - just use the Projects panel and switch their status back to Proposed then re-query on Reviewer. Others had this problem as well - following the documentation (which is incorrect as setting the status value ought to be the last step)! I will correct the documentation.
  28. Fix duplication in email messages, e.g.:
      > Subject: [THEON] Projects Escalating: Submission Late
      > 
      > Dear Tim,
      > 
      > 
      > The following projects are being tracked weekly and the time spent for the
      > previous period (from 01/10/2015 to 31/10/2015) was due to be entered
      > immediately after 31/10/2015 and is now late:
      > 
      > 313 - Pilot service for Yubikey two-factor authentication
      > 
      > Please follow the submission process now and enter time spent on these
      > projects in the last period.
      > 
      > This message has been copied to Alastair who will be in touch
      > soon to further discuss this delay.
      > 
      > The following projects are being tracked weekly and the time spent for the
      > previous period (from 26/10/2015 to 01/11/2015) was due to be entered
      > immediately after 01/11/2015 and is now late:
      > 
      > 311 - DICE environment for SL7
      > 207 - School Database Revamp: Phase 1B & 2B
      > 205 - Webmark Reform
      > 270 - Project Submission
      > 332 - CDT Software Requirements
      > 338 - ITO Progression BoE Reports
      > 353 - Port Research and Teaching Packages to SL7
      > 
      > Please follow the submission process now and enter time spent on these
      > projects in the last period.
      > 
      > This message has been copied to Alastair who will be in touch
      > soon to further discuss this delay. 
    or:
      > Subject: [THEON] Projects Submission Reminder
      > 
      > Dear Tim,
      > 
      > 
      > This is a reminder that the following projects are being tracked weekly
      > and the time spent for the previous period (from 01/10/2015 to 31/10/2015)
      > was due to be entered immediately after 31/10/2015:
      > 
      > 313 - Pilot service for Yubikey two-factor authentication
      > 
      > Please now follow the submission process as soon as you can and enter
      > time spent on these projects in the last period.
      > 
      > This is a reminder that the following projects are being tracked weekly
      > and the time spent for the previous period (from 26/10/2015 to 01/11/2015)
      > was due to be entered immediately after 01/11/2015:
      > 
      > 311 - DICE environment for SL7
      > 207 - School Database Revamp: Phase 1B & 2B
      > 205 - Webmark Reform
      > 270 - Project Submission
      > 332 - CDT Software Requirements
      > 338 - ITO Progression BoE Reports
      > 353 - Port Research and Teaching Packages to SL7
      > 
      > Please now follow the submission process as soon as you can and enter
      > time spent on these projects in the last period.
    both due to one monthly project and others weekly
  29. We should publish the start and end of projects in the systems blog, pointing people to project plan (at start) and final project report (at end). This is an extension of also having a subscribable mailing list for such announcements a'la the one from IS
  30. Below is probably a link to homepage (missing though see above) but it should be a link to the projects website full page project directory:
    > Subject: [THEON] Projects Completion
    > 
    > Dear Tim,
    > 
    > We are pleased to inform you that the following project which you submitted
    > is now officially complete:
    > 
    > 338 - ITO Progression BoE Reports
    > 
    > You can access the project completion report and other information here:
    > 
    >   
    > 
    > We hope you are happy with the results but if you have any questions or
    > anything to follow up please contact the relevant Unit Head.
  31. in email above include a URL link to project page below the number - description line
  32. notes on "micro" projects - submit with flag on form (possibly CO only) and means that bypasses review and approval stages, starts running immediately with daily monitoring with lead developer and manager as person that submitted ... concept is that these are for very lightweight (a few days) projects which are going to be done straight away by that person, if delayed then they should be flagged onto "wishlist" and started as necessary (by the project owner) - emails about effort reporting sent daily and created daily. Project can be marked as completed at any point by submitter without any formal process. Specific milestones can be added (project can't be closed unless met or they are changed/deleted). Very limited set of Standard milestones applied - not sure which ones. No oversight etc. Although will appear on projects list - will be at bottom in grey (not ranked) and no ranking/effort data is shown. These projects can also be added retrospectively if that is preferred (although that would still require correct sequence of events). Allows however that development effort is suitably contributed (always goes to submitters owning account holder - that will need line management structure added). Micro projects can be turned into full projects but that will initiate the usual review/approval/start process (but existing contributed effort will not be lost). Not sure about vice versa, suppose so as it won't matter really.
  33. approver needs to be able to see review - included in email and/or desktop, not appropriate for web page as not strictly public prior to actually approved.
  34. "As a suggestion: it'd be useful if these programmatically-generated emails contained hyperlinks to the named projects" - in reference to the "approved projects" email specifically, but should apply to any/all.
  35. "I only flipped it to finished on the 10th, the effort records for this week were created on the 7th. None were created for next week this Monday so this lot should be the last. We should just suppress these on completed status being reached." - in response to Alastair email complaining about still getting email requests for figures for a project with status=Finished.
  36. standard deliverable mandatory enforced before can start project running
  37. Effort - set a review point based on very rough effort estimate being hit or a duration of real time being hit.
  38. Add "comments" field into the Review panel so can be seen when reviewing.
  39. Add a "Meeting" desktop to allow minutes to be entered and meetings/talks status set.
  40. Note - need to pass down a param into the text with the tick frequency as the "weekly" is clearly just in the raw text below (first should be monthly).
    > Date: Tue, 4 Apr 2017 08:33:22 +0100
    > From: portal@theon.inf.ed.ac.uk
    > To: timc@inf.ed.ac.uk
    > Subject: Projects Submission Reminder
    > 
    > Dear Tim,
    > 
    > 
    > This is a reminder that the following projects are being tracked weekly
    > and the time spent for the previous period (from 01/03/2017 to 31/03/2017)
    > was due to be entered immediately after 31/03/2017:
    > 
    > 359 - SL7 server upgrade project - Research and Teaching unit
    > 
    > Please now follow the submission process as soon as you can and enter
    > time spent on these projects in the last period.
    > 
    > This is a reminder that the following projects are being tracked weekly
    > and the time spent for the previous period (from 27/03/2017 to 02/04/2017)
    > was due to be entered immediately after 02/04/2017:
    > 
    > 381 - Teaching Cluster Technology
    > 393 - Teaching Software 2016/17
    > 363 - Formalise and document prometheus/database interface
    > 359 - SL7 server upgrade project - Research and Teaching unit
    > 
    > Please now follow the submission process as soon as you can and enter
    > time spent on these projects in the last period.
  41. Add anchors in web pages with deliverable ids so can link directly to them, e.g. https://computing.projects.inf.ed.ac.uk/312/#1845
  42. See messages below - note that the second has been incorrectly embedded also into the first, must occur when different talk types are occuring at the next meeting for same person:
    > From portal@theon.inf.ed.ac.uk Mon Apr 24 10:03:28 2017
    > Date: Mon, 24 Apr 2017 10:03:26 +0100
    > From: portal@theon.inf.ed.ac.uk
    > To: gdutton@inf.ed.ac.uk
    > Cc: cms@inf.ed.ac.uk
    > Subject: [theon-portal] Projects Meeting Talks
    > 
    > Dear Graham,
    > 
    > 
    > Computing Projects Development Meeting
    > 
    > The meeting on Wednesday May 3rd 2017 has the following project talks on 
    > the agenda that you and/or any other assigned developers should be prepared 
    > to present.
    > 
    >   369 - Move administrative group filespace from AFS to Datastore
    >     Running Project Talk
    > 
    > Contact the relevant project manager to add a talk description and/or link 
    > to supporting materials.
    > 
    > If you are unable to present any of these talks at this meeting please 
    > advise the relevant project manager who can cancel the talk on your 
    > behalf.
    > 
    > The Computing Projects Development Meeting is usually held on the first and 
    > third Wednesday of every month at 10.00AM in IF1.16 for a maximum of one 
    > and a half hours. All COs and CSOs are encouraged to attend, and anyone 
    > leading a project should try to attend most meetings.
    > 
    > Computing Projects Development Meeting
    > 
    > The meeting on Wednesday May 3rd 2017 has the following project talks on 
    > the agenda that you and/or any other assigned developers should be prepared 
    > to present.
    > 
    >   205 - Webmark Reform
    >     Completion Project Talk
    > 
    > Contact the relevant project manager to add a talk description and/or link 
    > to supporting materials.
    > 
    > If you are unable to present any of these talks at this meeting please 
    > advise the relevant project manager who can cancel the talk on your 
    > behalf.
    > 
    > The Computing Projects Development Meeting is usually held on the first and 
    > third Wednesday of every month at 10.00AM in IF1.16 for a maximum of one 
    > and a half hours. All COs and CSOs are encouraged to attend, and anyone 
    > leading a project should try to attend most meetings.
    > 
    > Thank you
    > On behalf of CEG
    >
    > From portal@theon.inf.ed.ac.uk Mon Apr 24 10:33:30 2017
    > Date: Mon, 24 Apr 2017 10:33:27 +0100
    > From: portal@theon.inf.ed.ac.uk
    > To: gdutton@inf.ed.ac.uk
    > Cc: timc@inf.ed.ac.uk
    > Subject: [theon-portal] Projects Meeting Talks
    > 
    > Dear Graham,
    > 
    > 
    > Computing Projects Development Meeting
    > 
    > The meeting on Wednesday May 3rd 2017 has the following project talks on 
    > the agenda that you and/or any other assigned developers should be prepared 
    > to present.
    > 
    >   205 - Webmark Reform
    >     Completion Project Talk
    > 
    > Contact the relevant project manager to add a talk description and/or link 
    > to supporting materials.
    > 
    > If you are unable to present any of these talks at this meeting please 
    > advise the relevant project manager who can cancel the talk on your 
    > behalf.
    > 
    > The Computing Projects Development Meeting is usually held on the first and 
    > third Wednesday of every month at 10.00AM in IF1.16 for a maximum of one 
    > and a half hours. All COs and CSOs are encouraged to attend, and anyone 
    > leading a project should try to attend most meetings.
    > 
    > Thank you
    > On behalf of CEG
  43. Long single words without spaces (e.g. URLs) cause the line wrap formatting function to fall over (loop forever).
  44. In order to meet this action point: "add a standard deliverable aligned to the start of a project (rather than the end) to cover scoping" - need to update the feed function to support two standard deliverable types, one hooked to the end and one hooked to the start, as at the moment only the former works (is hard coded into the feed construction).
  45. When abandoning (cancelling) a meeting the individual talks must also be abandoned otherwise they continue to appear on web pages as an overdue deliverable and they will not be re-added as talks onto the next meeting agenda (get skipped, so the next in line appear instead). So this should be automated, if the parent meeting is abandoned the talk feed should have that status for each talk as well.
  46. Stop generating effort submit/commit records at the end of the current tick of a project once all deliverables have been met as these projects are just in holding for sign off at the next meeting but that might still be a while.
  47. It would be nice to be able to add a third co-developer. Or more generally any number may be sensible since the structure and reporting code will need to be changed either way.
  48. Once a project has been closed out it disappears from the "effort" panel, you then can't easily get to it to see what has been booked against it (for the purposes of writing the unit Tn report for example).
  49. New starting computing staff get a projects completion announcement message with a number of months backlog, this should have a time constraint on it so (like other messages) they only get stuff sent within that back period they have missed.
    > From: portal@theon.inf.ed.ac.uk
    > Subject: [theon-portal] Projects Completion Announcement
    > 
    > Dear NAME,
    > 
    > The following projects have now completed:
    > 
    > 168 - Password strength checks
    > 183 - Improved Bug Tracking Tool
    > 205 - Webmark Reform
    > 268 - Investigate AFS on ECDF storage
    > 287 - Securing School Web Servers
    > 299 - Local Forum Service
    > 311 - DICE environment for SL7
    > 312 - inf-unit initial SL7 work
    > 313 - Pilot service for Yubikey two-factor authentication
    > 339 - SL7 DICE Desktop
    > 348 - KDC software and configuration update
    > 352 - IPv6 investigation
    > 353 - Port Research and Teaching Packages to SL7
    > 356 - SL7 server platform
    > 357 - SL7 server upgrade project - Managed Platform Unit
    > 363 - Formalise and document prometheus/database interface
    > 375 - lcfg-nut overhaul for SL7 and SMSR
    > 377 - Port prometheus to SL7
    > 441 - Migration of Theon Course Feed to APT
    
  50. Seems to be a buglet with the "Projects Running" message when new projects start running some previously already running projects are included, probably related issue to above.
    > Date: Mon, 6 Nov 2017 11:02:05 GMT
    > From: portal@theon.inf.ed.ac.uk
    > To: gdmr@inf.ed.ac.uk
    > Subject: [theon-portal] Projects Running
    > 
    > Dear George,
    > 
    > We are pleased to tell you that the following projects which you submitted
    > have been prioritised and assigned, and active development has now started:
    > 
    > 312 - inf-unit initial SL7 work
    > The lead developer is Toby Blake (toby@inf.ed.ac.uk)
    > and the project is under the immediate responsibility of George Ross (gdmr@inf.ed.ac.uk).
    > 354 - Return to Appleton Tower
    > The lead developer is George Ross (gdmr@inf.ed.ac.uk)
    > and the project is under the immediate responsibility of George Ross (gdmr@inf.ed.ac.uk).
    > 375 - lcfg-nut overhaul for SL7 and SMSR
    > The lead developer is Ian Durkacz (idurkacz@inf.ed.ac.uk)
    > and the project is under the immediate responsibility of George Ross (gdmr@inf.ed.ac.uk).
    > 442 - Forum network switch upgrade
    > The lead developer is George Ross (gdmr@inf.ed.ac.uk)
    > and the project is under the immediate responsibility of George Ross (gdmr@inf.ed.ac.uk).
    > 443 - Prepare for GDPR
    > The lead developer is George Ross (gdmr@inf.ed.ac.uk)
    > and the project is under the immediate responsibility of George Ross (gdmr@inf.ed.ac.uk).
    > 444 - Bayes building network
    > The lead developer is George Ross (gdmr@inf.ed.ac.uk)
    > and the project is under the immediate responsibility of George Ross (gdmr@inf.ed.ac.uk).
    > 
    > During active development please refer any technical and progression
    > questions directly to the people listed above in the first instance.
    
  51. In the mailshot below 349 was starting but 363 had been running for a while (and effectively completed) so it should not have been included.
    ...
    We are pleased to tell you that the following projects which you submitted
    have been prioritised and assigned, and active development has now started:
    
    349 - Account Tidying
    The lead developer is Toby Blake (toby@inf.ed.ac.uk)
    and the project is under the immediate responsibility of George Ross (gdmr@inf.ed.ac.uk).
    363 - Formalise and document prometheus/database interface
    The lead developer is Tim Colles (timc@inf.ed.ac.uk)
    and the project is under the immediate responsibility of Tim Colles (timc@inf.ed.ac.uk).
    ...
    
  52. There are probably some bugs related to tick frequency being changed after a project has started.
    Not sure - the switch is probably not immediate, i.e. you will need to
    see out this month weekly but the records should be generated monthly
    from next month or something like that. But nor would I be surprised if
    there were bugs associated with a mid period accounting transition.
    
    Lets see what happens from 1st Jan ...
    
    Tim
    
    On Wed, 13 Dec 2017, George Ross wrote:
    
    > > The following projects are being tracked monthly and the time spent for the
    > > previous period (from 04/12/2017 to 10/12/2017) was due to be entered
    > > immediately after 10/12/2017 and is now late: ...
    >
    > Looks like a theon bug to me.  I switched the accounting to monthly, but
    > we're still being asked about this weekly period.
    

Done List

These were all on the list but have now been done/fixed in one way or another.

  1. Split off HoC email from MPU email - e.g. by using hoc@inf alias instead of "ascobie" lookup for escalation type and approval check type messages.
  2. Fix "owner" so deadlines for deliverables are not read only - actually split deliverables into specific/standard where specific can be edited freely and added/deleted but standard remain read only (one month from max of specifics).
  3. Add project number onto computing.projects index and project page
  4. never sent - tricky to fix in current framework unless trigger a "pre-complete" status when all deliverables met and then use that status change date to trigger message instead - or better simply rely on sent message archive and continual resend using the new receipt mechanism (see #))
  5. Fold committment properly (don't re-accrue, i.e. committment with some left first contributes to leftover before adding) - this is not so good for previous system projects
    • not done in quite this way tho, committment is reset to minimum of committment/submitted at end of each period
  6. Handle a "pending" status as result of review, with corresponding email and web pages (not on main)
  7. finished projects web page (separate, like pending)
  8. may be covered above but for reviewed but not yet approved projects:
    • "I still can't find it in http://computing.projects.inf.ed.ac.uk/#331 ?"
    • "Thats correct as it is not public yet (e.g. you won't see 315, 317 either) - arguably it should still be listed there in some fashion as it is still effectively "under review" - added to the list of improvements (set aside a day this month to work through a few of those) - we should"
  9. need a completion report index page for all projects on computing.projects
    • (links to the actual final reports)
    • presumably satisfied by 19 above
  10. when a project moves to running during an accounting period the spawn does not create a committment record for that period, just the next period, however it may only have happened at the start and effort may be being committed in the current period so one should be created
  11. need "completed" projects list with homepage snapshot index
    • as per 19 and 23 ...
  12. allow specific deliverables to be owner added/modified etc
  13. organise deliverables into two boxes on desktop - specific and standard
  14. auto set standard deliverable deadline to max of all specific deliverables plus month
  15. in rankings over time absorb week periods with zero effort into the most recent period back with some effort - at the moment the display is very on/off striped (even if the off and on periods are not the same they look the same), if we absorb zero weeks (hence spread the last effort block prior to zero across the zero weeks as an average) this will look better and rank better probably
  16. green new projects at bottom isn't quite right (presumably as unranked so far) - also some have star (new), some don't - why?
    • new ones now at top - although date check not quite right
  17. On the "running" message have a direct link to the full project descriptor page.
    • Also modified to an aggregated message type.
  18. when waiting/running for N days is 0 (same day) looks wrong, remove phrase altogether if less than 24hrs
    • done, not committed/deployed
  19. comments aggregation in cop_project_feed should use _tag for name (not _xtag) but could usefully retain square brackets and put date/time in there).
  20. oversight message summary table should include "submitted to date" as a percentage of committment to see which are closing in or not ... another reason to send these out on the Friday to ensure inclusion of most recent submission data (or on Monday but based on Friday)
  21. Not possible to see "review reason" anywhere - should be on generated project web page and/or ui desktop - shown on the new "approved" project page, still not shown prior to this
  22. switch to receipted mail mechanism so messages are not triggered by specific date and are
    • resent automatically as necessary
  23. add validation so a project cant move to running unless lead developer and owning account assigned (these are shown on "running" message so need set)
    • - not quite, added an anomaly report instead
  24. Enforce homepage for projects before can be "started"
    • - not quite, added an anomaly report instead
  25. lead developer and manager must be assigned before switch to Running allowed so avoiding gaps in data, as in email above (this example does not have gaps)
    • - not quite, added an anomaly report instead
  26. if >1 project submitted by the same person are simultaneously approved they will get a message with multiple approved text bodies - need to aggregate down as per others
  27. Change all status date fields to timestamps and use generic receipted delivery for messages and run more frequently - need to investigate a trigger/event method for doing this ...
  28. completed projects are only broadcast once on the day after the latest deliverable date when all deliverables "complete" - problem being that all deliverables may not be updated until after this date meaning message never sent - tricky to fix in current framework unless trigger a "pre-complete" status when all deliverables met and then use that status change date to trigger message instead - or better simply rely on sent message archive and continual resend using the new receipt mechanism (see #52) - or auto-set met date to 'today' if not specfically
    • updated - probably better to use receipt stuff
  29. Like above this one needs aggregated properly:
    > Subject: [theon-portal] [THEON] Projects Running
    > 
    > Dear Alastair,
    > 
    > We are pleased to tell you that the following project which you submitted
    > has been prioritised and assigned, and active development has now started:
    > 
    > 361 - SL7 server upgrade project - Infrastructure unit
    > 
    > The lead developer is George Ross (gdmr@inf.ed.ac.uk)
    > and the project is under the immediate
    > responsibility of George Ross (gdmr@inf.ed.ac.uk).
    > During active development please refer any technical and progression
    > questions directly to these people in the first instance.
    > 
    > This project will now run until completion. You can view the list of currently
    > running projects and activity here:
    > 
    >   https://computing.projects.inf.ed.ac.uk/
    > 
    > From time to time other projects may receive prioritised active
    > development over this one. To learn more about the project process,
    > the prioritisation of projects and the allocation of effort to them,
    > see:
    >  
    >   http://computing.help.inf.ed.ac.uk/projects
    > We are pleased to tell you that the following project which you submitted
    > has been prioritised and assigned, and active development has now started:
    > 
    > 360 - SL7 server upgrade project - User Support unit
    > 
    > The lead developer is Alison Downie (alisond@inf.ed.ac.uk)
    > and the project is under the immediate
    > responsibility of Alison Downie (alisond@inf.ed.ac.uk).
    > During active development please refer any technical and progression
    > questions directly to these people in the first instance.
    > 
    > This project will now run until completion. You can view the list of currently
    > running projects and activity here:
    > 
    >   https://computing.projects.inf.ed.ac.uk/
  30. Fix duplication in email messages, e.g.:
    > Subject: [THEON] Projects Completion
    > 
    > Dear Tim,
    > 
    > We are pleased to inform you that the following project which you submitted
    > is now officially complete:
    > 
    > 303 - AT3/4/5 decant to FH
    > 
    > You can access the project completion report and other information here:
    > 
    >   http://www.dice.inf.ed.ac.uk/units/infrastructure/Projects/303-ATFHdecant/
    > 
    > We hope you are happy with the results but if you have any questions or
    > anything to follow up please contact the relevant Unit Head.
    > We are pleased to inform you that the following project which you submitted
    > is now officially complete:
    > 
    > 304 - AT6/7/8 decant to somewhere
    > 
    > You can access the project completion report and other information here:
    > 
    >   http://www.dice.inf.ed.ac.uk/units/infrastructure/Projects/304-AT678decant/
    > 
    > We hope you are happy with the results but if you have any questions or
    > anything to follow up please contact the relevant Unit Head.
    > We are pleased to inform you that the following project which you submitted
    > is now officially complete:
    > 
    > 345 - USU - Decant
    > 
    > You can access the project completion report and other information here:
    > 
    >   
    > 
    > We hope you are happy with the results but if you have any questions or
    > anything to follow up please contact the relevant Unit Head.
    > We are pleased to inform you that the following project which you submitted
    > is now officially complete:
    > 
    > 342 - Services - Decant
    > 
    > You can access the project completion report and other information here:
    > 
    >   
    > 
    > We hope you are happy with the results but if you have any questions or
    > anything to follow up please contact the relevant Unit Head.
    > 
    due to multiple completions on the same day
  31. Add "recent talks" onto project pages: covered by below
  32. Add "talks due" email message to CEG (and pending on web pages ... ?): covered by below
  33. live agenda page, talks poll/agenda announce messages: covered by below
  34. Revise projects talks mechanism. Schedule talks based on amount of effort done in project since last talk, qualified by when did last talk (for any project) plus also include talk close to impending deadlines and at start (and at end once project ended auto-schedule the completion talk), also projects with no effort in long time, e.g. long time since last talk. These get automatically added by feed as standard deliverables (specific talk deliverables can also be added). Add a deliverable type which is something like 'Project' (existing ones), 'Meeting' for talks and 'Action' for actions (also now added as project deliverables). Can then do meeting agenda from talks, actions and completions data ... ?
  35. the "deliverable" sync is only triggered on "project" changes, not "deliverable" changes meaning when the end dates are pushed back the standard deliverable deadline dates are not automatically shifted to a month following the latest deliverable end date, need to add a trigger on "deliverable" date changes
  36. nothing seems to trigger/run the deliverable feed couple, e.g. to update deadlines, requires manual intervention, see also 62 above
  37. Committment reminders to be offset by working days
    • done, not committed/deployed

-- TimColles - 17 May 2017

Edit | Attach | Print version | History: r10 < r9 < r8 < r7 < r6 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r9 - 15 Dec 2017 - 08:53:29 - TimColles
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback
This Wiki uses Cookies