-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
Hi folks,
Thanks for your continued support and feedback, we wanted to give you an update on the status of this issue.
Over the medium term, the direction we're taking with Crowd is to focus on scalability, reliability and performance. Unfortunately, it means that this feature is unlikely to be included in any near-term improvements to the product, as workflows and management don't align with our future direction.
We've decided to close this issue because we feel that by leaving it open, there's undue expectation that the issue is being actively worked on, and we don't want to give you the wrong information. We are aware of the issue, and recognise that it is something that needs to be done, however, it's unrealistic that it will ship within the next 18 months.
Regards,
Eugene
Atlassian Product Management
At present, the implementation of roles in Crowd is identical to the implementation of groups. Additional development work would be needed to differentiate the functionality of roles from groups.
We need to consider allowing role-based access control via Crowd.
Request to all Crowd customers and users:
- Please add a comment to this issue and let us know how you'd like to use roles.
- blocks
-
- Closed
[CWD-931] Enhance the role-based access control in Crowd
| Workflow | Original: JAC Suggestion Workflow [ 3388770 ] | New: JAC Suggestion Workflow 3 [ 3630830 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Simplified Crowd Development Workflow v2 [ 1393360 ] | New: JAC Suggestion Workflow [ 3388770 ] |
| Assignee | Original: David O'Flynn [Atlassian] [ doflynn ] | |
| Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
| Workflow | Original: Crowd Development Workflow v2 [ 273801 ] | New: Simplified Crowd Development Workflow v2 [ 1393360 ] |
Eugene Mak [Atlassian]
added a comment - Hi Dave,
Just to clear things up - Crowd is definitely not going away from our product set. For a small team, Crowd represents an unnecessary barrier to adoption. We've worked to ensure that teams of under 500 users don't need Crowd.
However, Crowd still represents an extremely important part of our product set for larger and more complex installations, for example if you have a large number of users, or multiple instances of JIRA or Confluence.
Currently Atlassian has no plans to enhance roles in any of our applications, which is why we've updated the issue with the current statement.
We've figured bad news is better than no news.
Regards,
Eugene
Eugene Mak [Atlassian]
added a comment - Hi Dave,
Just to clear things up - Crowd is definitely not going away from our product set. For a small team, Crowd represents an unnecessary barrier to adoption. We've worked to ensure that teams of under 500 users don't need Crowd.
However, Crowd still represents an extremely important part of our product set for larger and more complex installations, for example if you have a large number of users, or multiple instances of JIRA or Confluence.
Currently Atlassian has no plans to enhance roles in any of our applications, which is why we've updated the issue with the current statement.
We've figured bad news is better than no news.
Regards,
Eugene I have to say I'm confused more than anything. It looks like most of Crowd is being implemented directly in Jira and soon the other Atlassian products (beyond just Confluence) will be able to leverage Jira for authentication. Despite statements to the contrary, this leads me to speculate that Crowd might be going away at some point. Will other applications will be able to leverage the roles defined in Jira? Maybe this is the reason crowd-based roles are now marked as "won't fix"? I think a good solid statement of direction would help.
Brian Topping
added a comment - Eugene,
I think the deafening silence in response to the exciting updates is because everyone that had high hopes for the issue and contributed strong time and energy to helping make Crowd something really competitive. Instead, they've been given a wet noodle in return for their efforts, years later than anyone had ever thought it would take to implement them.
Sorry for the splash of cold water back at you, but I'm just sayin. There's nothing exciting to see here, and if anything, people are doing you a favor by not commenting on the decision.
Brian
Brian Topping
added a comment - Eugene,
I think the deafening silence in response to the exciting updates is because everyone that had high hopes for the issue and contributed strong time and energy to helping make Crowd something really competitive. Instead, they've been given a wet noodle in return for their efforts, years later than anyone had ever thought it would take to implement them.
Sorry for the splash of cold water back at you, but I'm just sayin. There's nothing exciting to see here, and if anything, people are doing you a favor by not commenting on the decision.
Brian
Eugene Mak [Atlassian]
added a comment - Hi everyone,
Just letting you know that we've updated the current Atlassian status in the description of this issue, and you should go check it out!
Eugene Mak
Atlassian Product Management
Eugene Mak [Atlassian]
added a comment - Hi everyone,
Just letting you know that we've updated the current Atlassian status in the description of this issue, and you should go check it out!
Eugene Mak
Atlassian Product Management Eugene Mak [Atlassian]
made changes -
| Description |
Original:
At present, the implementation of roles in Crowd is identical to the implementation of groups. Additional development work would be needed to differentiate the functionality of roles from groups.
We need to consider allowing role-based access control via Crowd. Request to all Crowd customers and users: * Please add a comment to this issue and let us know how you'd like to use roles. |
New:
{panel:title=Atlassian Status as of 27 April 2011|borderStyle=solid|borderColor=#3C78B5| titleBGColor=#3C78B5| bgColor=#E7F4FA}
Hi folks, Thanks for your continued support and feedback, we wanted to give you an update on the status of this issue. Over the medium term, the direction we're taking with Crowd is to focus on scalability, reliability and performance. Unfortunately, it means that this feature is unlikely to be included in any near-term improvements to the product, as workflows and management don't align with our future direction. We've decided to close this issue because we feel that by leaving it open, there's undue expectation that the issue is being actively worked on, and we don't want to give you the wrong information. We are aware of the issue, and recognise that it is something that needs to be done, however, it's unrealistic that it will ship within the next 18 months. Regards, Eugene Atlassian Product Management {panel} At present, the implementation of roles in Crowd is identical to the implementation of groups. Additional development work would be needed to differentiate the functionality of roles from groups. We need to consider allowing role-based access control via Crowd. Request to all Crowd customers and users: * Please add a comment to this issue and let us know how you'd like to use roles. |
Eugene Mak [Atlassian]
made changes -
| Resolution | New: Won't Fix [ 2 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
I need the ability to distribute the administration of groups. This way those admins would have control over adding/removing users from their group without having to be a JIRA/Confluence/Crowd admin. This would be similar to how Jira allows project admins to place users into roles for their project.