Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Component/s: tracker.moodle.org
    • Labels:
      None

      Description

      this plugin would be really useful!
      https://plugins.atlassian.com/plugin/details/5218

      I'd like to be able to add automatic watchers to the SCORM component (other than myself as the lead)

      posted in HQ Chat:

      23:15:29) dan: https://plugins.atlassian.com/plugin/details/5218
      (23:18:03) moodler: please file a bug to have that added to our install, it looks useful
      (23:30:12) david: yeah - and it will slow down JIRA a bit more :-p (just kidding, sounds really useful)

        Activity

        Hide
        Jordan Tomkinson added a comment -

        Plugin is installed but disabled

        Will re-enable it after the move of fisheye today

        personal note: https://studio.plugins.atlassian.com/wiki/display/JCWP/JIRA+Component+Watcher+Plugin

        Show
        Jordan Tomkinson added a comment - Plugin is installed but disabled Will re-enable it after the move of fisheye today personal note: https://studio.plugins.atlassian.com/wiki/display/JCWP/JIRA+Component+Watcher+Plugin
        Hide
        Jordan Tomkinson added a comment -

        plugin installed.

        Show
        Jordan Tomkinson added a comment - plugin installed.
        Hide
        Dan Marsden added a comment -

        Thanks Jordan! - can you please add "matteo" as an automatic watcher to the SCORM component?

        Show
        Dan Marsden added a comment - Thanks Jordan! - can you please add "matteo" as an automatic watcher to the SCORM component?
        Hide
        Jordan Tomkinson added a comment -

        Done!

        Show
        Jordan Tomkinson added a comment - Done!
        Hide
        Dan Marsden added a comment -

        I'm not sure if it's working - I just created MDL-26201 but it doesn't seem to have added Matteo as a watcher...yet anyway - how quickly should the listener make the change?

        Show
        Dan Marsden added a comment - I'm not sure if it's working - I just created MDL-26201 but it doesn't seem to have added Matteo as a watcher...yet anyway - how quickly should the listener make the change?
        Hide
        Matteo Scaramuccia added a comment -

        Hi All,
        at the time of this comment I'm not yet a watcher of MDL-26201.
        I'll manually add myself tomorrow, my evening (Italy => CET => GMT +1): feel free to play with the plug-in settings using my account as the target of your tests (we have a test case) and please advice me in case you don't want me to perform any manual update.

        Show
        Matteo Scaramuccia added a comment - Hi All, at the time of this comment I'm not yet a watcher of MDL-26201 . I'll manually add myself tomorrow, my evening (Italy => CET => GMT +1): feel free to play with the plug-in settings using my account as the target of your tests (we have a test case) and please advice me in case you don't want me to perform any manual update.
        Hide
        Matteo Scaramuccia added a comment -

        FYI: MDL-26253, manually set as a watcher of.

        Show
        Matteo Scaramuccia added a comment - FYI: MDL-26253 , manually set as a watcher of.
        Hide
        Matteo Scaramuccia added a comment -

        FYI: I can confirm that the automation doesn't work, at least for my account. Manually set as a watcher of MDL-26595.

        Show
        Matteo Scaramuccia added a comment - FYI: I can confirm that the automation doesn't work, at least for my account. Manually set as a watcher of MDL-26595 .
        Hide
        Matt Sharpe (Inactive) added a comment -

        I've taken a look at how the plugin works and what else is around, it definitely can only be done by adding it in the admin interface rather than allowing users to opt for it themselves. I'll get this plugin installed for JIRA 5 as the way it works in current tracker is a bit more complicated and requires a restart of JIRA.

        I'll get back to you on progress.

        Show
        Matt Sharpe (Inactive) added a comment - I've taken a look at how the plugin works and what else is around, it definitely can only be done by adding it in the admin interface rather than allowing users to opt for it themselves. I'll get this plugin installed for JIRA 5 as the way it works in current tracker is a bit more complicated and requires a restart of JIRA. I'll get back to you on progress.
        Hide
        Matteo Scaramuccia added a comment -

        I'm available to help you, if I can do something : feel free to use the account matteo to setup him (me) as a watcher of something. My focus is SCORM but to test the plug-in you can add me as watcher of anything will be useful for you: I'm actually used to put me as watcher fo several issues out of SCORM so no problem if I'll be elected watcher of something not decided by me, manually.

        Show
        Matteo Scaramuccia added a comment - I'm available to help you, if I can do something : feel free to use the account matteo to setup him (me) as a watcher of something. My focus is SCORM but to test the plug-in you can add me as watcher of anything will be useful for you: I'm actually used to put me as watcher fo several issues out of SCORM so no problem if I'll be elected watcher of something not decided by me, manually.
        Hide
        Dan Marsden added a comment -

        Thaknks Matt - a big advantage (at least for me) would be to have all component leads automatically added as watchers - esp if it sends an e-mail on creation of the bug - this means when people add multiple components to the bug we would all get notified of the issue and be able to triage/fix component list if required.

        Show
        Dan Marsden added a comment - Thaknks Matt - a big advantage (at least for me) would be to have all component leads automatically added as watchers - esp if it sends an e-mail on creation of the bug - this means when people add multiple components to the bug we would all get notified of the issue and be able to triage/fix component list if required.
        Hide
        Matteo Scaramuccia added a comment -

        Has there been some progress?
        I've seen e.g. MDLSITE-1976 to have the assignee (Aparup Banerjee) also set as a partecipant which've recalled me this issue.

        Show
        Matteo Scaramuccia added a comment - Has there been some progress? I've seen e.g. MDLSITE-1976 to have the assignee (Aparup Banerjee) also set as a partecipant which've recalled me this issue.
        Hide
        Matt Sharpe (Inactive) added a comment -

        I'm not sure what that issue has to do with this? There is no progress. As I mentioned earlier, this is on hold for JIRA 5.

        Show
        Matt Sharpe (Inactive) added a comment - I'm not sure what that issue has to do with this? There is no progress. As I mentioned earlier, this is on hold for JIRA 5.
        Hide
        Matteo Scaramuccia added a comment -

        Hi Matt,
        no relation at all: just guessing about the strange association, i.e. the assignee: is also a partecipant but... yesterday I did not focus that it was a partecipant and not a watcher as I was thinking when I submitted my comment (my poor brain). Sorry for the noise!

        Show
        Matteo Scaramuccia added a comment - Hi Matt, no relation at all: just guessing about the strange association, i.e. the assignee : is also a partecipant but... yesterday I did not focus that it was a partecipant and not a watcher as I was thinking when I submitted my comment (my poor brain). Sorry for the noise!
        Hide
        Matt Sharpe (Inactive) added a comment -

        No problem Matteo, I'll comment here when we go live with JIRA 5.

        Show
        Matt Sharpe (Inactive) added a comment - No problem Matteo, I'll comment here when we go live with JIRA 5.
        Hide
        Matthew Spurrier added a comment -

        Just came across this, component watcher wasn't installed on our new system, i've installed it now.
        Can anyone tell me whether this ticket is still relevant/should still remain open?

        Thanks

        Show
        Matthew Spurrier added a comment - Just came across this, component watcher wasn't installed on our new system, i've installed it now. Can anyone tell me whether this ticket is still relevant/should still remain open? Thanks
        Hide
        Matteo Scaramuccia added a comment -

        Hi Matthew,
        I'm not allowed to say anything about policies but I suggest to configure Dan Marsden and Matteo Scaramuccia as watchers of the SCORM component, to recall the initial request.

        I guess that HQ will shortly provide a list of watchers for the other components: AFAIK the main issue is that when the ticket is assigned to others than the main maintainer she/he is involved no more in the ticket unless she/he is set as a Watcher BEFORE reassigning the ticket i.e. my suggestion is to configure this plugin to include at least the official component mantainer also as a watcher for her/his component.

        HTH,
        Matteo

        Show
        Matteo Scaramuccia added a comment - Hi Matthew, I'm not allowed to say anything about policies but I suggest to configure Dan Marsden and Matteo Scaramuccia as watchers of the SCORM component, to recall the initial request. I guess that HQ will shortly provide a list of watchers for the other components: AFAIK the main issue is that when the ticket is assigned to others than the main maintainer she/he is involved no more in the ticket unless she/he is set as a Watcher BEFORE reassigning the ticket i.e. my suggestion is to configure this plugin to include at least the official component mantainer also as a watcher for her/his component. HTH, Matteo
        Hide
        Dan Marsden added a comment -

        Thanks Matthew - IMO each component lead should be added to their related components as auto-watchers - one of the issues I have is when someone reports something against multiple components and one of those includes SCORM I don't usually get notified - It would be really nice to have this done automatically! - Michael might have some other thoughts too.

        Show
        Dan Marsden added a comment - Thanks Matthew - IMO each component lead should be added to their related components as auto-watchers - one of the issues I have is when someone reports something against multiple components and one of those includes SCORM I don't usually get notified - It would be really nice to have this done automatically! - Michael might have some other thoughts too.
        Hide
        Matthew Spurrier added a comment -

        No worries Dan, what I've done is wrote a script that automatically goes over and adds project leads to the watchers if they're not one.
        I've run the script, and all components in the system for every project now have project leads as watchers.

        Hope that helps.

        Show
        Matthew Spurrier added a comment - No worries Dan, what I've done is wrote a script that automatically goes over and adds project leads to the watchers if they're not one. I've run the script, and all components in the system for every project now have project leads as watchers. Hope that helps.
        Hide
        Dan Marsden added a comment -

        brilliant - thanks Matthew!

        Show
        Dan Marsden added a comment - brilliant - thanks Matthew!
        Hide
        Matthew Spurrier added a comment -

        This request has been completed

        Show
        Matthew Spurrier added a comment - This request has been completed
        Hide
        Andrew Nicols added a comment -

        Does this script run fairly regularly? I was assigned an issue earlier (MDL-38349) at 10:08 GMT. I think I was probably assigned as I'm the component lead for AJAX and JavaScript, and A comes before F, R, and U (the other components) even though the File Picker was the more relevant component to the issue. None of the other component leads have been automatically added as watchers.

        Andrew

        Show
        Andrew Nicols added a comment - Does this script run fairly regularly? I was assigned an issue earlier ( MDL-38349 ) at 10:08 GMT. I think I was probably assigned as I'm the component lead for AJAX and JavaScript, and A comes before F, R, and U (the other components) even though the File Picker was the more relevant component to the issue. None of the other component leads have been automatically added as watchers. Andrew

          People

          • Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development