in my newly created MantisBT I created 2 categories. One for bugs and one for tasks. While the bugs should be reported by any user who wants to, the tasks should be only accessible by developers.
So, is there any way to make a category not visible for users with a certain access level?
Edit: Maybe to make this more general, how can I set what a certain access level is allowed to do?
There is no support for 'private' categories in MantisBT at the moment. I suggest that you
create two Projects, Tasks and Bugs
set the visibility of the Bugs project to 'private'
add only the developer to the Bugs project
Related
I am a new user of confluence, I participate in an workflow in witch customer support receives bugs, I report them to a central team of developers. Now, the thing is I am trying to create a way for the customer support team to have more visibility on the issues that I report, as in to quickly find out the status of a certain issues. What I have in mind is a confluence page consisting of a table of the issues extracted from Jira but I am having trouble reaching the exact end product that I have in mind. For example is there a way for me to make a column to this table so I can add comments for some issues? or can I categorize the issues by which pack of developers are they assigned to. Mainly I want to know if there is an alternative way of going about my situation and I don't see it because of my lack of experience.
Thanks!
Rather than adding comments in Confluence I would suggest you instead add them to the Jira tickets and then display them on Confluence.
The Jira Issues macro allows you to chose the fields you display. You could, for example, add a 'Confluence comment' custom field to your Jira tickets and make sure this is shown in Confluence.
As for categorizing issues, this is best done by using filters. The approach would be as follows:
Decide what categories you want
Create a filter for each category
Use the Jira Issues macro multiple times, once for each of the filters
I created a Group using
https://learn.microsoft.com/en-us/graph/api/group-post-groups?view=graph-rest-1.0&tabs=http
and then used
https://learn.microsoft.com/en-us/graph/api/team-put-teams?view=graph-rest-1.0&tabs=http
to create a Team. Now I am facing issue when adding a plan using a Planner app
"Failed to create the plan."
How I can fix this issue?
In my investigations, I found that the other team members are able to create plans. As an owner of the team, I am not able to create them. if I am trying graph API I'm getting an error:
You do not have the required permissions to access this item, or the item may not exist.
I'm glad you came right and that I was able to help. I'm updating the answer so that it's more clear on a few points:
Technically, this actually has nothing to do with Teams at all, it relates to Office 365 Groups, which forms the core underneath Teams, Planner, and more. You actually link in your question to the Groups docs, incidentally. I've updated the question title to reflect this.
I haven't tested this exactly, but I doubt that it needs your account exactly in the Owners and Members - I suspect the main constraint is that there needs to be at least one person in each of those roles (that means there has to be at least one Owner and at least one Member). Arguably, this is actually a bug in Planner, but it was maybe never detected by Microsoft because if you create a Group from the web interface, it automatically puts your user in as Owner and Member.
If you do put your own account into both positions, but that's not what you want long term, you could probably just take them out after creating the Planner plan.
Just a reminder that best practice is to have more than one owner of a Group, in case/when the original Owner is not/no longer available.
It's fixed after adding the creator of teams as a member too. So I had to add the user who is creating Teams in Team members too.
I made sure that there was another owner on the Team, demoted and removed the owner and the re-added them to the team. This resolved the issue that I had with multiple teams
we use Asana as our internal project management platform. We would like to use it to interact with our clients so they can see the progress of their projects - which is the same per year. We created the Kanaban view and move the cards through each process. We would like to show this to our clients, but have them only see their card.
Is there a way of doing this?
Thanks
There isn't a way that I'm aware of to have only certain tasks show up to certain people within a project - our access control is limited to the project level, so everyone who can see a project can see all tasks in a project.
One thing you might consider as a workaround is to multi-home the tasks into multiple projects (that is, add them into multiple projects). In this way you can limit membership to the second project to only the people in that set of clients, and have your original project as a master board with just your team in it.
You will have to keep these projects in sync, but this is possible in our API. Our tasks/addProject endpoint accepts both a project and a section (which is admittedly a bit unintuitive). If you maintain a mapping of each section, that is, "ID of Column A in the master board view maps to ID of Column B in the client board view", you can periodically iterate over all your tasks and re-insert each task in the client board view in the correct column based on where the task is in the master board view. (addProject is idempotent across requests, so re-insertions into a project are OK).
This is an interesting use case, thanks for sharing it! Hopefully this workaround will prove to be usable.
I would like to customize a Work Item Type in TFS to automatically set the Assignee to a particular role. For example (to compare to another Issue Tracker), in JIRA the default Assignee is the Project Lead (so that any ticket not otherwise assigned, gets automatically assigned to whatever person is designated in the role of Project Lead). Can I do something similar in TFS?
So, I realize that one difference between JIRA and TFS is that TFS doesn't (to my knowledge) have the concept of "Roles". The closest thing to that is "Groups", but unlike Roles, Groups can have multiple people (which may be the restricting factor in this problem). I know how to configure a TFS Work Item so that only a certain Group gets listed in the "Assign To" field, but I would like to go a step farther, if possible, and create a custom Group with just one member (e.g., "Issue Guru") and then set up the work item to get automatically assigned to that person.
I'm trying to replicate the Jira functionality here, and maybe there is just no good way to do it in the TFS framework. Any suggestions?
There's a Step by Step Guide on Ivan Fioravanti's Blog for enabling it.
If you are unfamiliar with customising Work Item Types, have a look at the following links (stolen from Grant Holliday's blog).
I never tried this in production but here is something I tried quickly and it seems like it could work.
You can set the default value to a Group by editing work item template in template editor.
Just select Assigned to field and add a DEFAULT rule like shown in the image below.
This will also require you to create one or more groups (one global or maybe one per project). Once you set this up you won’t have to make any updates in the future but only manage people who are in the groups.
What is the best way to store a task for multiple users in TFS 2010 ? I can only assign one for one task.
(for example: when I plan a demo to all developers)
(this is a scrum Msf Agile project, where the task is part of a user story)
I'm sorry to tell you that you can't assign multiple users to a single work item out of the box; At the same time, I do not recommended trying as this, as it does not fit the model in TFS. The conventional / recommended way to handle this type of scenario is to create multiple tasks; one for each developer in this case. You can easily accomplish this by copying a set of tasks using MS Excel. Another option (given the example you used) is to create a "Meeting" work item that has multiple drop-downs - one for each person that would attend meetings like for a demo or a technical review.
Yet another option is to create a custom control to format and store a list of users. This would likely be relatively complex to maintain, as you have to distribute it to each user's machine (it will need to be installed locally), and last I checked you would need 2 versions; one for the Team Explorer user interface and another for the Web Access tool that most people use to create work items from a web page on their TFS server. Future updates to TFS could possibly break your custom control. It is rarely worth the effort. Another downside is the you would likely be limited by how you can use MS Excel to work with the data you store in the field that the custom control works with. If you want to look into this further you can find some examples in the following CodePlex project: http://witcustomcontrols.codeplex.com/
You might consider your true goals in tracking such things as meetings and other items you want to assign multiple people to. Tasks are the heart of tracking progress of user stories in the MSF Agile Template. Tracking meeting attendance does not typically relate directly to a User Story, for example; so it won't typically assist you to determine how much close you are to being "done" with a User Story. If you want to take advantage of the existing reports, then you should organize your tasks so that they roll up as child work items to User Story (or Bug) work items.
Short story: you can't. Work items in the Process Template of Microsoft are designed to target nobody or only one User.
Now you can customize the Process Template to change this.
Take this post for instance, the customization works for group. But I don't recommend you to do so because TFS is basically not designed for that and you may end up disappointed.