It's my understanding that if you are a project administrator you will see the ADMINISTRATOR menu option but will not be able to administrate particular users.

You've given Jeremy full admin privs for Jira. I would make sure that infra is ok with that, just in case.


Regards,
Alan

On Oct 22, 2009, at 6:19 AM, Joe Bohn wrote:

Hi Jeremy,

It looks like you were somehow removed from the admin group. I added you back in and hopefully things will work better.

Joe


Joe Bohn wrote:
Yes, it is my understanding that if you have jira-admin should be able to edit group membership.
You can do this in two ways:
1) Go to the user browser and search for the user. You can then select "Groups" under the Operations listed per user from the search results where you can perform "join" or "leave" functions. You can also select the specific user and at the bottom of the user panel there is an "edit groups" option. 2) Go to the group browser. You can find the group you want to work on and then select edit members. So do you not see these options in the group and user admin views? I'll look at your id so see if I notice anything strange.
Joe
Jeremy Hughes wrote:
Hi Joe, I'm interested as to how you did this. Presumably it's because you are in the jira-administrators group. A few years ago I was given admin karma and I have the ADMINISTRATOR menu option along the top of
the JIRA web page. I can add users to the different roles
(Administrators, Committers etc) but I can't modify groups such as
aries-developer. It feels like I'm in some kinda admin purgatory.

When I look at the my dashboard it looks like I'm not in
jira-administrators group, so I'm wondering now how I've managed to
get the ADMINISTRATOR menu item on my dashboard!

Any ideas?

Cheers,
Jeremy

2009/10/21 Joe Bohn <[email protected]>:
Adam,

I just added you as an aries-developer so you should be able to assign the jira to yourself now. You may need to log-out then back in to jira.

Joe


Adam Wojtuniak (JIRA) wrote:
  [
https://issues.apache.org/jira/browse/ARIES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768462 #action_12768462
]
Adam Wojtuniak commented on ARIES-29:
-------------------------------------

If someone can assign this task to me I can start working on it . thanks.

Implement JMX Agent
-------------------

              Key: ARIES-29
              URL: https://issues.apache.org/jira/browse/ARIES-29
          Project: Aries
       Issue Type: New Feature
       Components: JMX
 Affects Versions: 1.0
         Reporter: Adam Wojtuniak
          Fix For: 1.0


Implement JMX Agent. It should be responsible for tracking all MBean servers(registered as a services) and services which will be exposed as a
Managed Beans (MBeans).
JMX Agent should register following MBeans: Framework MBean, Bundle State MBean, Service State MBean, Package State MBean, Permission Admin MBean,
Configuration Admin MBean,
Provisioning Service MBean, User Admin MBean, Conditional Permission
Admin MBean.
It is open issue if we should track MBean servers registered as services but for now we can follow RI of JMX which listen to MBean Server services. For now we can track MBeanServers and when service is discovered register MBeans. Same in case when service is exposed as Managed MBeans it should be
registered (on all available MBean servers) when is discovered.



--
Joe

Reply via email to