Report on issues

In this video, you will learn how to create:

  • An issue report showing resolving objects
  • A project report showing converted issue information
Transcript
Many traffic and project managers create a custom report to centralize open issues submitted to a particular request. You. This makes it easy to track what’s new and what needs attention. a report of projects that have been created to resolve issues can show converted issue information. There are several videos that go into detail about how to create clustered reports. See the link to the text after this video. But I’m just going to walk through the steps to create one issue report and one project report with a few handy fields For people who manage issues, the first report is the issue Report it shows whether or not an issue has been assigned and also if it’s been converted to resolving object. The resolving object is either a task or a project. If the issue has been converted to a task or project, link to that resolving object will appear in this column. When the resolving object is completed, the issue will be resolved and it will fall off. This report issues that do not have a resolving object. Are either still waiting to be converted or they will be resolved without being converted by the person assigned. The issues are sorted by entry date, so the newest issues will appear at the top of the list. To create this report. Click on reports from the main menu. look on new report issue. Report were brought to the Collins view area initially it we want to add resolving object to the columns. Click on add column over here. so here we type in resolving object. we choose resolving object here under issue. And now we can move this where we want it. Just kind of move it over here. There are some other columns that we don’t need, like actual completion. When something is completed, it’s going to fall off this report. So we don’t need to show that date you want to sort by entry date. So we’ll click on entry click sort by this call and we’ll choose descending so that the most recent entries show up at the top And that’s it for the columns. We’re not going to do any groupings. Next we go to filters. We don’t want to see all of the issues in the system. We just want to see ones that are coming from the video request request queue. So we’re going to add a filter rule. We want to know the project idea associated with an issue, and we want to know if that Project ID is equal to video requests, liability letters, and then select the project next thing we want to know is if the issue is already complete. We’ll add another rule type in the word complete or start typing it in. We want to choose is complete, so we only want to see issues where is complete. This false. Well, choose save Now the properties for a name if we haven’t already named it, we’re going to call this video request Resolving object issue report to save it. And there’s our report. The next report is projects with converted issue information. This report shows only projects that have been converted from issues, so these projects are the resolving objects of the issues. We can see some information about the issues they were created to resolve. We can see whether the original issue was entered, the name of the issue and the name of the person we requested. We could also see some useful information about how the project is coming along to create this report, Click on reports from the main menu. This time will choose new Report Project Report, It will start by adding a column. This will be the converted issue entry date. We could start typing here. Entry date and their entry dates for the project were a whole bunch of other things and also for the converted issues. This is the one we want to choose and we’ll bring it over here. Add another column. this one will be the converted issued name. Well, this is a name and it could be of the project or any of these other things. But we want the converted issue names or choose it from here. Then we’ll bring it over here. Next column will be the converted issue originator name. That’s the name of the person who made the original request. So again, we can just type name here and scroll down to the object we want, which is the converted issued originator name. This will include the first and last name. Well, this over here, we’re not going to really need the description, we’ll get rid of that and we’ll add a couple of more things that are interesting, like the status of the project. it over here and then let’s do the progress status as well. This tells us if it’s on time or not, now we’re done with the views Now for filters. We only want to see projects that were converted from an issue where they’re converted. There will be a converted issue originator entry date that we can get. So what we’ll do to start with is we’ll make sure that in this project that we’re looking at, is there a converted issue originator entry date? But when we look at this field, we want to see if it exists or not. So if it’s not null, then we’re good. That means there is a date for the converted issue originally. So it was originally created by somebody and then that issue was converted to the project that we’re looking at right now. we’ll add an additional filter rule. We only want to see projects that are not complete so we can type is complete. And we want to choose false statement clothes. we call this project’s was converted issue information to and there you go
recommendation-more-help
c9fbcf61-6d19-481e-a9ab-f54a0ae0ee8a