I have 14 people in 5 teams. Some are overlapping. i.e A couple of Web team members are part of the Server team.
I am not sure if this is the right way, but I would like to manage each team with their own Jira project.
Thus, I have 5 projects:
Mobile
Design
Web
Server
Hardware
I would like to assign access to projects based on Group. i.e. Mobile project should only be accessed by a Group name Mobile Developers. Design project should only be accessed by the Design Team Group. Design should NOT have access to the Mobile project.
How do I accomplish this on Jira Cloud?
Currently I have two Permission Scheme:
Default software scheme shows all 5 of my projects. I can only edit the Name and Description. When I click on Permissions it takes me to a screen that says:
How can I assign permission to each individual project based on Group?
Clone your default permission scheme and create a custom permission scheme for each project.
For example:
Mobile Project Permission Scheme
Next, assign the new permission schemes to the projects. So the Mobile project uses the Mobile Project Permission Scheme, the Web project uses the Web Project Permission Scheme, etc.
At this stage, there is no new behaviour as all the projects are using the same permission scheme, just they now have their own copies of the scheme. That means any changes you make to a custom permission scheme will only impact on one project.
Now, edit the permission schemes and give permissions based on the groups.
e.g.
Manage Sprints - Mobile_User_Group
Related
I'm currently developing a gmail add-on and am hoping to allow a few users internal to my team to test out the add-on prior to a public release. I was following the documentation here from google that states
You can allow other users to test the add-on by sharing the Apps Script project with their account (read access is required) and then prompting the users to follow the above steps.
I assume that 'read' access is equivalent to 'view' access, and have given a user 'view' access to the project.
The problem I'm running into is that even with 'view' permissions, users aren't able to do a test deployment and install the add-on to their gmail account. The blue 'Deploy' button simply isn't visible. Any ideas on how to get my add-on into a few users hands before publishing, but without giving them edit privileges?
One way to do it is to have the users copy your script and deploy it.
Another is to publish the Add-On privately and you would have control over what version of the Add-On your test users are seeing. For this your users should be of the same Google Workspace domain
I am looking at automating Group creation using Graph API in Teams. I can successfully do that by using following API
const result = await client.api('/groups').post(group);
What I am looking for is creating a Tab in that Group and then adding an Organisational app (Internal App) into that tab.
Here is the link for creating tabs in teams but could not see anything on adding app into that tab
https://learn.microsoft.com/en-us/graph/api/teamstab-add?view=graph-rest-1.0
Is it possible ? and if so, where can i see APIs and relevant documents.
Basically, to add a Tab, you need to have the content of that tab configured and waiting. There are two ways to do this:
point to a website directly - this would be equivalent of using the "Website" option in the UI to add a tab, and then inserting the address of the website. This is kind of what the Graph endpoint sample you linked to is doing, but you need to use the payload specified here. See the answer over here for more info: Channel Tabs in Teams through Graph-API
Use an existing registered App in Teams that has a "Tab" functionality. The same link I gave above has options for doing this, like Planner, or Word, or whatever. You would be able to do the same thing for your own custom app, but then the app needs to be built, and installed into the tenant app catalog (i.e. the internal company "store"), or the Teams "App Store". Read more about that here
I want to develop an Microsoft Teams app which will use Graph API and publish it to Market Place, all articles I have read suggest this integration require Application Registration on Azure Portal of a specific tenant. However, how can I register the application if the application is published, i.e. not for any specific tenant?
Yes, this is definitely possible. If you look at the screenshot in this article (just below where this link will take you), in the screenshot is show "Accounts in this organizational directory only". You want to choose the OTHER option: ""Accounts in any organizational directory".
Depending on what your app does, you will need some kind of authorization though, either from the user(s) or from the administrator, in the end-user's tenant.
We are using TFS 2013.
We can assign users to the project by going to the web portal dashboard of the project, and click on Manage and add members to team.
Other way is to click on the gear icon on top right and manage users from there.
Another way is to open the TFS admin console and assign permissions from there.
I would like to know the differences between these 3 approaches. Thanks.
It doesn't appear that you can modify the base url for the portal settings in TFS 2010. I currently have
http://tfsserver.mydomain.com
I would like the system to launch
http://tfsserver
instead when a user selects 'Show project portal' from Team Explorer.
Is it possible to change the site root that it points to? We keep getting security prompts with fqdn.
I found the answer myself. On the application tier, open the admin console, select SharePoint Web Applications and change the base url there.