MDMS Related

Can we merge code (PR) into "develop" branch in the last 2 days of sprint?

• No

• Yes. If it is bug fixes or urgent changes by BA/PO approval

• Yes. If the development just finish last minute

• Yes. If you think it is simple changes

Why can't we merge codes into "develop" branch in last 2 days of sprint?

• Quality control. So QA can create automation script.

• Just extra own preference step

• Quality control. We hope that 2 days can let QA & PO to verify the changes. And we can revert before cutting the release branch.

• Quality control. So Build Master can mange the DB script execution

If I created a new system rule only for TEST3 . What is the proper process?

• Raise DB action item and link to JIRA ticket with "dependency_with_dba" label. Put comment in Build Master Dependency

• Raise DB action Item

• Just execute direcly to TEST3 will do

• Raise DB action item and link to JIRA ticket with "dependency_with_dba" label.

If teamate request me to review his/her PR into "develop" branch, what to do ?

• Review properly , click approve , merge and delete branch

• Review properly and click approve.

• Just click approve PR since teamate said is testing code purpose. He/She will remove later.

• Ensure got proper ticket for such changes. Using Code Review Template as checklist. Provide constructive feedbacks for coding.

I found that my PR was approved by teamate yesterday but no comment in my ticket. What should I do ?

• Merge and delete branch. Deploy to DEV and inform ready for test in teams

• Ping reviewer to use code review template and place comment check list in my ticket. Once done , if not code freeze period can merge and delete branch. Deploy to DEV and inform ready for test in teams

• Ping reviewer to use code review template and place comment check list in my ticket. Once done ,can merge and delete branch. Deploy to DEV and inform ready for test in teams

I am working one bug ticket that from CDT environment. What should I do ?

• Using investigation template to put the findings. If confirm is bug then fix else pass it back to Akondi/BA/PO to confirm the requirements.

• Just fix and request to re-test.

• Using investigation template to put the findings. Apply fixes and also configuration change. Merge it into "develop" branch

I had done the fixes for one CDT bug ticket. Template used. Test cases added...

• Merge the changes to the reported "branch" and "develop" . Deploy to both DEV & CDT .

• Just merge the changes into "develop" and deploy to DEV

Today I am supporting X market to change configuration in PROD/GLOBAL QA. Changes already in place as urgent...

• Log the issue details in my support ticket .

• Log the issue details in my support ticket . Raise DB Action Item. Comment in Build Master Dependency ticket.

Today I got one changes to configuration, when I put the comment in Build Master Dependency ticket found out the ticket already over the Sprint (based on title- last sprint.)...

• Place comment as usual and ping respective Build Master to alert him/her

• Edit my old comment in Dependency ticket.

• Edit the script will do since already mentioned and linked in Dependency ticket.

If there is new GUI report needed as usual need PDF and excel, I just need to ensure main and sub-menu in DB Action Item and Build Master Dependency will do.

• Yes

• No