Comments
-
See https://confluence.atlassian.com/display/JIRA/Customising+Email+Content
-
Add a "user picker" custom field to the system (or multi-user picker). They're both standard custom fields for JIRA, so you can find them when clicking "add" on the list of custom fields. Once you've added the field, you'll be able to use it in permissions, security schemes (for visibility) and the notification scheme (for…
-
No. As I said, you'd need to hack the code.
-
Oops - another option would be to downgrade your admins to ordinary users and set up a system that can automatically create users without allowing edit. I've done that as a JIRA project before. Needs, a bit of code to handle user-create as a post-function and we did it with an email handler too, but it works well.
-
If there were plugins that could do it, I wouldn't have said "no". Admins have admin rights, and that includes updating user profiles. Atlassian are looking at making it more configurable, which will lead to many different types of admin, but I suspect the right to edit users will still be bundled with the right to add and…
-
Nope, there is no way to do this without hacking the core code to block the modify functions. The usual approach here is to simply "trust your admins".
-
I'm afraid you've missed every point made above, and I'm not going to repeat it all over yet again. There is no need to implement a design that allows for bad things to happen, use a custom field to help with information about other users, and stop trying to shoot yourself in the foot.
-
When someone says always, I say the same thing. I think this is the only conversation where I've ever repeatedly said Everyone. Because, I really do mean it. Everywhere I've seen multiple owners of an issue, an "I thought someone else was responsible for it" event has occurred. Glad you've found the associated-person…
-
I should also emphasise it's just the assignee that matters. Who is the currently responsible person? You should never allow a state where a group people can say "but I thought the other one was responsible". Because in real life, it happens. And a lot more than people think it does. By all means have other fields for…
-
It's been discussed at length above. No-one has yet come up with a scenario where multiple assignees cannot go wrong. No, I've not done an exhaustive survey, I just speak from decades of experience in several fields, which is that everywhere that allows multiple assignees has had problems with it. Everyone here who has…
-
Yes, I am, except you're de-emphasising the scale of the problem. I'm not saying "because I've seen a real-world problem", I'm saying "Everyone has seen this problem". A better analogy would be more like "we know eating too many foxgloves kills everyone who does it, so let's not sell it as food in all our supermarkets".
-
>Maybe in some average situations. If by "average" you mean "all real world cases", yes. I've yet to find anywhere where "i thought someone else was looking at it" has not happened. It's not a double standard, it's real-world deliberate design.
-
Sorry, yes, pairing is the exception, as you're working closely together. But you still don't need multiple assignees for it in real life, because you're so close. I like the idea of having a field for "other half" and displaying both avatars on the board.
-
And, yet again, what happens when both of them think the other one is dealing with it? It's fine to have multiple interested people, and your display would be a good move. But multiple assignees always introduces the problem and your solution does not fix that.
-
In an ideal world, you work together well on things and you know who is ultimately responsible for an issue. In a lot of places that works fine, and people mostly ignore the assignee field because it's not important, because they know that the team is working together. There's no point in worrying about the field in those…
-
It's not really them trying to be the law, they've chosen not to implement something in their software. There are several ways of adding associated or interested people or groups, but the principle of a single user being the responsible party is the important one, and one that no-one arguing for multiple assignees here has…
-
I can't imagine any scenario where it's of use to other team members while it's in-progress with a pair.
-
You've still missed the point, sorry. Could you re-read the last comment? Where you should realise that while pairing is the one case where it's valid, it's also of no use, because you're paired, so it doesn't matter.
-
Pair programming is one of the cases where it might make sense in abstract terms. But, as you're working that closely together, it's unnecessary, so why break it for all the other cases where multiple assignees do not work in real life? (p.s. add a user picker for "partner" if you want to record the other half of the pair)
-
Yes - that's exactly how most people do it and it works fine. You have one single assignee (primary) which changes over time, and then other people who are involved as secondaries. It's not multiple assignees, it's single assignee with others.
-
It's not about agile methodologies, I'm just trying to understand why people want this function when it really doesn't work (or isn't needed) in real life. Yes, that's an opinion, but it's based on many years of seeing multiple-assignees fail miserably and repeatedly. So far, no-one has given a scenario where it can work…
-
I think you're missing the point. In your organisation, you're communicating well - that's great. Because you're doing that well, you don't need multiple assignees In places where communication is less than ideal, you don't want multiple assignees because that allows things to go wrong. In real life, there is still no case…
-
Right. So you don't need two assignees because they're working well together. You have the assignee as the single point of contact and responsibility, even though they're working with someone else. That scenario means you don't need multiple assignees, and my "who's working on it" problem doesn't exist. In real life, this…
-
Again, pair programming is a good case for having associates. But still not multiple assignees - you'll be working close enough that the current assignee will always be able to tell anyone what the other is doing. >Also the point about 2 people thinking the other is working on a task breaking the process is just an…
-
So when someone says "who's working on it?" and both of them say "the other one", you have a broken process. You've described another very good case for having participants or colleauges or helpers additionally named, but still no scenario where multiple assignees work in real lift.
-
So, when you have two assignees, which one of them is ultimately responsible? It does make sense to have many people who might need to work on it, in different roles, and people who are involved for various reasons. But more than one assignee fails.
-
In the real world, multiple assignees does not work. Can you honestly tell me that you have never once had any situation where A and B are assigned something and one of them doesn't deal with it because the other one should have? Or have two assignees accidentally duplicate effort? You say "task owner" and "helper". That's…
-
I think this has been answered to death. Multiple assignees don't work in the real world because there's no clear responsibility. It can be very useful to have secondary assignees as well, but in reality you always want a single owner.
-
2 years, it must have crept ahead of the official page!
-
Googol != Google :-)