I want to make ticket number fixed for the different enterprise that can be easy to look at.
The problem I'm facing is when you try to sort the ticket Ids for one enterprise you will find different ticket number so I went to make sequence no arrangement.
eg: I want to adjust the ticket number from (1-1000) to one of my enterprise and (1000-2000) to other one is this possible on mantis ticket.
If this is about the MantisBT bug tracker, you can't partition by ids. I suggest you create different projects for each enterprise if you don't want them to be mixed.
If you need them in the same project, then use different categories and sort the issues by category.
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 are migrating from an in-house tool to Jira for managing our scrum board, and we have concerns that I have been unable to resolve by searching the Internet. But you folks are smart, right? ;-)
Our current scrum board shows the usual swim lanes across state columns (for todo, progress, review, done). Each swim lane represents a user story, and has a link to (and a snippet of) the user story description in Jira. It also has a number of 'tickets' (these would be subtasks in Jira lingo) that start in 'todo' and move across to eventually end up in 'done'.
So far, Jira can do all of this, too (although creating sub-tasks is rather a lot more work in Jira than in our in-house tool). However:
When we commit code, we include a ticket ID in the commit message, and thus each ticket displays a list of commits that were done to complete that particular ticket / partial story. I haven't been able to find out how to do this in Jira -- if it's possible at all. Instead, it seems one must open a sub-task to see if there are any commits on it?
Each commit also shows its review state, which gives us an excellent overview of how close to done a ticket really is. I haven't been able to find out how to do this in Jira -- if it's possible at all. Instead, it seems one must open the sub-task, and drill down further into Fisheye(?) in order to see the review state?
In total, our tool provides a one-screen overview of the state of each user story, ticket, commit, and review state; and it's very lightweight to pull in new stories (from Jira) and add tickets. We fear that Jira is not able to provide such a one-screen overview, forcing us to open Fisheye in order to know whether a given commit has passed review.
Is it really true that Jira must be this cumbersome?
For reference, here is what a single ticket (subtask) looks like in our system:
And if you look at the whole scrum board, it's actually quite easy to get a feel for the number of commits on individual user stories and tickets, and the ratio of pending/passed/failed code reviews:
I agree with your fears when you say
We fear that Jira is not able to provide such a one-screen overview
In my experience (7+ years with Jira/Agile) I've not seen a such condensed view of information about a sigle user story even on a swimlane with relative cards.
Also in the Atlassian marketplace there seems to be no good plugin to solve your issue, even partially.
To make such move from your in-house tool to Jira retaining all you have there, I fear you should develop a custom Plug-in using Jira SDK to integrate with the agile boards.
It may be enough to start by developing a custom field to show what you need from a "ticket" (ie sub-issue) and trying to insert it into one of the three "slots" available for cards (I mean Rapidboard card layout configuration screen).
If you wanna try, start from here.
Another option to create a new custom field would be the Adaptavist Scriptrunner plugin. It will ease the building of custom fields: your new field can be written also in Groovy rather than plain Java. I've used it to build an extended status custom field (just to give the user an immediate big picture of it) that informs him in plain english and with stylish css colors why an issue is blocked or anything else relevant, getting data from other fields or linked issues that are not immediately visible to the user. IMHO, it is very similar to your problem.
We're about to implement TFS 2012 and I've been having some fun customizing some work items to aid us in our reporting. One issue we have is our reporting based on clients.
Our Product Backlog Items keep our requirements, however, we need to report our requirements per client (government regulations). Some requirements will affect all clients, some will only reflect certain ones. I've been able to add a global list of clients along with a multi-select option and that part is working great.
The issue is we need to also note the requirement number for each selected client. I know I can go in and add a field for each 'Client Requirement', but as that list gets bigger, that screen will be insanely huge.
Does anybody know of such a way to implement something of the sort?
One option would be to create a custom Work Item Type for Clients. Then link your PBI's to the appropriate client WI's. When you create a link you can enter a link comment also which you could use to capture the client-specific requirement number.
I would create a custom "Client Requirement" work item that has the list of clients to select and includes a field for Client ID. You can then either use the related link type or create your own, maybe "Implements \ Implemented By" so that you can create a Reporting Services report that pulls the ID's
I have an app developed for Android and iOS; both have their own JIRA projects.
I'd like to be able to create single user stories in Greenhopper and assign them to both projects, without cloning/linking like I do today.
Is there a way to do this, or a recommended approach?
I think if you better define your end-goal, such as "If a user story incorporates iOS, it should show up in X dashboard and Y filter" or "users should be able to access X filter of related issues from story details view", you may get more concrete answers.
Maybe you have a user Story from an Android user who can't see his profile picture, so you create it in the Android project. After gathering feedback, you find out they originally uploaded an unsupported file type from his friend's iPhone. At this point, you could create an iOS issue, or story, and link it to the original Android story (you mentioned that's not optimal though), or you could add the new iOS information to the original Android ticket.
If you define the complications that these methods would create, it would be easier to offer workarounds for your specific problems. It is possible using JQL (the Jira query language) to return results from multiple projects in a single filter, and that particular filter can be reported on. You can also use labels or a custom field to report on issues across projects, and then use those JQL (filter) queries in Greenhopper/Jira Agile.
https://confluence.atlassian.com/display/AGILE/Configuring+Filters