Wiki Forum Sign up! Explore Home

Not signed in (Sign In)

LiveSearch

Welcome, Guest

Want to take part in these discussions? Sign in if you have an account, or apply for one below

Vanilla 1.1.2 is a product of Lussumo. More Information: Documentation, Community Support.

    • CommentAuthordax
    • CommentTimeJul 30th 2007 edited
     permalink
    It would be nice to be able to select the "default" notifiers in the project add/edit page. That way the people selected are automatically selected when a new issue is created. The user can always change it on a per issue basis as they do now, it just preselects.

    Along the same lines, the list of notifiers in this project window and the existing task mechanism should only show people with read rights to the project the task is assigned to.

    Dax
    • CommentAuthoradmin
    • CommentTimeJul 31st 2007
     permalink
    Both those issue should be doable, just need to refresh the notify list on project change and remember people who were selected.

    -- Erlend
    • CommentAuthordax
    • CommentTimeAug 1st 2007
     permalink
    I would think the defaults are only populated on task creation. After that, it is as set by the issue editing process. I can remove them all or add, etc. I guess you could do what I'm requesting and also have an ALWAYS notify option that gets notified no matter what. That's less important to me, but could be useful.

    Dax
    • CommentAuthordax
    • CommentTimeAug 5th 2007
     permalink
    Any chance on the filtered notification list to match the people that have project access being implemented? My list of potential notified people is getting long and I've got people asking "who's this person?"
    • CommentAuthoradmin
    • CommentTimeAug 5th 2007
     permalink
    Yeah, it's doable, I just need to refresh the list if you change projects.

    -- Erlend
    • CommentAuthoradmin
    • CommentTimeAug 5th 2007
     permalink
    Done.

    -- Erlend
    • CommentAuthordax
    • CommentTimeAug 5th 2007
     permalink
    Dang Erland, you rule. I appreciate the quick help.

    Dax
    • CommentAuthordax
    • CommentTimeAug 5th 2007
     permalink
    Quick question, are all these quick changes you make in the source control immediately or do you update that periodically?

    Dax
    • CommentAuthordax
    • CommentTimeAug 5th 2007
     permalink
    I created a new issue on the default project that came up in the drop down (in other words I didn't change the project drop down). The Notification and the Assign to fileds showed me 4 users (all supposed to be on the list), but there are more. If I change the project dropdown to another project, those other areas update, if I change back to the original project I see the proper list of users (more then the original 4). FYI.

    Dax
    • CommentAuthoradmin
    • CommentTimeAug 5th 2007
     permalink
    Hmm, I'll have a look tomorrow. My testing was showed the correct users in all cases, so it's something you're doing differently. Maybe the other users only have read access?
    • CommentAuthoradmin
    • CommentTimeAug 5th 2007
     permalink
    I commit my changes to Darcs as soon as I believe they work, then keep updating that until I'm convinced they work, then deploy it to the live server. And if there's a problem, I immediately commit my fixes to Darcs again, and the server as soon as possible.

    The source repository might get a few commits which are experimental from time to time, and those aren't deployed on the server until they're complete. And it'll get commits on new features (which might be hidden from the interface) as soon as I have something written, weather it works or not.