I'm working on a project that's got a great JIRA setup and awesome buy-in of everyone for the agile development process. The issue I'm having is that tickets stack up in code review. I'd like to be able to see who code reviewed what, much like I can see who has closed out which tickets.
I know that metrics are there to be used for good and not evil, so I want to do this to ensure that people spending time code reviewing are properly credited instead of that time not being recognized at all.
Currently, everyone who does code review assigns themselves to the ticket (which is unassigned upon being placed into the "Ready for Review" workflow state), so at some point there is a record of them working on it. Is this a good way to track the reviewers and is there a way to get aggregate information this after the fact? If not, is there a better way of representing this information in JIRA?
Thanks!
A simple solution would be to add a custom field called 'Code Reviewer' of type select a user. You would be able to search on that and report on it.
You could workflow it so that when the issue is transitioned out of your 'Code Review' status a window pops up containing only the "Code Reviewer' custom field to be completed.
What you need to do:
Create a new custom field - this is done in the 'Issues' configuration menu. Ensure your custom field uses the 'select a user' type.
https://confluence.atlassian.com/display/JIRA/Adding+a+Custom+Field
Create a new Screen - this is also done in the 'Issues configuration menu. On your new screen you need to make sure that the only field that is visible is your new custom field.
https://confluence.atlassian.com/display/JIRA/Defining+a+Screen
Edit your workflow. Find the transition from out of 'Code Review' and associate it with your custom screen.
https://confluence.atlassian.com/display/JIRA/Configuring+Workflow
The result will be that when a user transitions out of 'Code Review' they will have the custom screen pop-up. They can then select the name of the person who did the code review and this will be populated in the custom field.
Related
The CRM365 Form displays a convenient document template dropdown button where a number of actions could be initiated. Additionally, it displays the list of already existing document templates. The user can select one template in the list and it is downloaded locally by your browser. So far all good.
Our goal is actually to select the template, retrieve it, and create it in a Document Management repository. We have a working solution for this but it involves too many pieces and steps so we are looking for some better ideas.
Ideally we are looking for a solution where we can:
"intercept" the click on the template item and run a JavaScript function
If we find a solution to this, the rest would be just calling our custom workflow to do the rest of the job.
So, is there any way to hook that "select/click" event from the form menu?
Thank you very much for your help and advice.
when i check the application status history tab of New Business License application ,i got confused by the same statuses multiple times. When clicking the form only we came to know who returned/approved the form? Is there any way for the user to know from the history tab itself without clicking on the form
There is no other option as of formsflow.ai v4.0.4 to show what changes are modified in case of monitoring Application History.
It depends totally upon the workflow you design, how the applicationStatus changes across each stage of workflow. So if you are confused by multiple status happening at same time, you can redesign the workflow in such a way.
Is there a way to remove the option to select a menu link for specific fields?
For example I have a dashboard that has details of each users action and a few of those users are actually an automated system. So the few that are part of the system do not need to be reviewed as those are always automatic.
I want to only allow this menu selection for actual users and not the few "accounts" that are part of an automated system.
The kind of menu link on selection I am talking about.
Is it possible to remove this menu link for only specific values in a column?
I don't think it's possible - am fascinated to know if someone comes in with a way to do it - so one option to consider is renaming to "Daily Details - ignore for Bot 1 & 2" so the users are aware they should do nothing.
When we are doing the customization of a work item type in VSTS. Do we also have the ability to track the history of the customization itself?
For example, we are trying to find out when the start date field was added to our customized Bug work item type.
A field was not there in a previous Increment but we noticed it recently. Just want to find out if there is a date captured somewhere that tells us when it was added or who may have added it?
Unfortunately we cannot get the information from VSTS for now. No date or history included from the retrieved process information via REST API.
However there's already a user voice submitted here to suggest the feature to add Activity Log to VSTS to track user accesses, you can go and vote it up or submit a new one to suggest the feature again to achieve that is future release.
For now as a workaround we suggest that you can ask the team members to add corresponding comments in description area after completing the customization for the process... Thus you can track the history of the customization...
I've just started in FM 14. I have a client table and a project table. When I look at a client entry I have a portal that shows me the titles of the projects they have commissioned. I'd like to be able to click on one of the projects in that portal list and be taken to the layout that contains all of the other fields in that project record. Can this be done? Is this enough information?
Yes. Set the button action as a script step "Go to Related Record". In this script step, set the table as "projects" and select the layout you would like to go.
I would stay away from GoToRelatedRecord. I usually just grab the ID from the item in the portal, then search for that item on a new layout, then do whatever I planned on doing. It's safer. With GoToRelatedRecord you can never really control what happens.