POKE ME for any consultancy

Thursday, March 28, 2024

What are types of MIS?

 


Management Information Systems (MIS) is the study of people, technology, organizations, and the relationships among them

Five components comprise a management information system:
 people, business processes, data, hardware, and software

Here are some types of management information systems:

  • Management reporting system
    This system provides business information in the form of reports and statements to help management members. Management reports can help set strategic goals for each employee or department and track progress towards meeting these goals.
  • Process control system
    This system monitors various processes across a production line, gathering data to report on the performance of the system. Process control systems are also called industrial control systems (ICS).
  • Sales and marketing system
    This system helps track sales figures and advertising effectiveness. It also helps understand distribution channels and customer response, which can help marketing managers gauge projected sales and develop strategies for future improvements.
  • Inventory control system
    This system helps businesses manage their inventory levels. It tracks the number of items in stock, when they need to be reordered, and when they are sold. It also keeps track of the cost of the items and the amount of inventory that has been sold.
  • Accounting and finance system
    This system is an automated computerized system to process all financial and accounting-related tasks in an organization. It tracks a company's assets and investments, assisting with functions like financial statement generation and tax compliance. ,
Google Analytics ,Google Calendar, Basecamp ,Google Docs,Evernote ,Power BI

Wednesday, March 20, 2024

jira interview questions

 1) Explain what is JIRA?

JIRA is an issue tracking product or a software tool developed by Atlassian, commonly used for bug tracking, project management and issue tracking; it is entirely based on this three aspects.

2) Explain what is a workflow?

Workflow is defined as a movement of the bug/issue through various stages during its life-cycle

Created/Open

WIP ( Work In Progress)

Completed/Closed

3) What can be referred as an issue in JIRA?

In JIRA, an issue can be anything like a

Software bug

The project task

A help-desk ticket

The leave request form

4) List out the source control programs with which it integrates?

It integrates with source control programs such as CVS, Git, Subversion, Clearcase, Visual SourceSafe, Mercurial, and Perforce.

5) Why use JIRA?

The reason behind using JIRA is

Upfront and fair licensing policy

Features that is not available elsewhere

Get latest update on the progress of projects

It run anywhere and recognized with many famous companies

Easily extensible and customizable


6) Is it possible to access JIRA cloud site via a mobile device?

Yes, it is possible to access JIRA cloud site via a mobile device. You have to just use the URL of the JIRA cloud site in your mobile web browser.

7) Can you disable JIRA mobile for the site?

You can disable JIRA mobile for the site, so that users can be unable to operate the desktop view of JIRA on their mobile device.  JIRA mobile comes as a system add-on and can be disabled any time.

8) Explain labelling and linking issue in JIRA?

Labelling Issue: It enables you to categorize an issue in a more informal way than assigning it to a component or version. You can then search issues according to label.

Linking Issue: This feature enables you to link an association between two issues on either on the same or different JIRA servers.

9) Mention the types of reports generated in JIRA?

JIRA offer reports that show statistics for projects, versions, people or other fields within issues.  Various reports included with JIRA are

Average Age Report

Pie Chart Report

Resolution Time Report

Recently Created Issues Report

Resolved vs. Created Issues Report

Single Level Group by Report

Time Tracking Report

User Workload Report

Workload Pie Chart Report, etc.

10) Explain what is Cloning an Issue?

Cloning as issue allows you to create a duplicate of the original issue so that many employees can work on a single issue within a single project. The clone issue can be connected to the original issue.  A clone issue holds following the information

Summary

Description

Assignee

Environment

Priority

Issue Type

Security

Reporter

Components, etc.

11) Mention what things are not included in cloned issue in JIRA?

Time tracking

Issue history

Comments

Subtask

Issue Link

12) Explain what is the use of “Move Issue” wizard in JIRA?

The move issue wizard enables you to specify another project in your JIRA instance. Move wizard permit you to change certain attributes of an issue like

Issue Type: If your issue is a custom issue type and does not occur in your target project, you must choose a new issue type for your issue

Issue Status: If you have assigned your issue as a custom issue status and it does not exist in your project, you must select a new issue status for your issue

Custom Fields: If you have determined required custom fields for your issue, which do not occur in the target project, you must set values for them.

13) How security setting is helpful in JIRA?

JIRA’S security setting restricts the access to the issue to only those people who is allowed to work on the issue or a member of the chosen security level. Security level of an issue can be set either when the issue is created or when the issue is being edited

14) Explain how you can share an issue with other users?

You can email an issue by using the share option in JIRA. You can also email other JIRA users a link to the issue by sharing the issue with them or by mentioning them in an issue’s Description or Comment field.

15) Explain how you can modify multiple bulk issues?

To modify multiple bulk issues, you can use Bulk Change option from the “Tools” menu of the navigator.  All the issues on the current page can be selected for the bulk operation.  The following list details the available bulk operations like

Workflow Transition

Delete

Move

Edit

16) Explain how you can disable mail notification for Bulk Operations?

To disable mail notification for a particular Bulk Operations, you have to de-select the “Send Notification” checkbox in the bulk operation wizard.

17) What does an issue change history include?

Issue change history includes

Deletion of a comment

Deletion of a worklog

Creation or deletion of an issue link

Attachment of a file

Changes to an issue field

18) Explain what does the three color indicates tracking times or duration for an issue?

Three color will be displayed representing the amount of time spent behind the issue

Original Estimate (Blue): The amount of time originally estimated to resolve the issue

Remaining Estimate(Orange): The remaining amount of time left to resolve the issue

Time Spen or Logged (Green): The amount of time spent so far while resolving the issue

19) Mention some of the popular add-ons for JIRA?

Some popular add-ons for JIRA include,

Suites utilities for JIRA

ScriptRunner for JIRA

Zephyr for JIRA – Test Management

JIRA Toolkit Plugin

Atlassian REST API Browser

Portfolio for JIRA

JIRA Misc Workflow Extensions

Tempo Timesheets for JIRA

JIRA Charting Plugin

20) Mention what is Schemes in JIRA?

Schemes are a major part of JIRA configuration. It is a collection of configured values that can be used by one or more JIRA project. For instance, Notification Schemes, Permission Scheme, Issue Type Scheme, and so on. There are total seven types of schemes.

JIRA:

·         How can I force developers to update resolution status before close the tickets?

·         How to check the list of deployed tickets be automatically updated in JIRA?

  • How can I call external rest api of azure devops from JIRA cloud .For example to create release from JIRA cloud workflow in azure devops

·         Can we create a scenario in jira when build fails then ticket status move back from "In Progress" to "To DO" else if build pass ticket status move to “Done”

·         Is that possible to show the release of all the projects into one page?

·         Program manager need to see all running sprints in a project ?make a filter that would automatically select all running sprints?

·         Explain different filter-board filters, sub-filters, and quick filters?


Thursday, February 15, 2024

What is DevSecOps?

 DevSecOps is the practice of integrating security into a continuous integrationcontinuous delivery, and continuous deployment pipeline. By incorporating DevOps values into software security, security verification becomes an active, integrated part of the development process. 


https://www.atlassian.com/devops/devops-tools/cicd-tools

Thursday, February 1, 2024

Set up a CI/CD pipeline for cloud deployments with Jenkins

 


To set up a CI/CD pipeline for cloud deployments with Jenkins, you can follow these general steps:

1. Install Jenkins: Set up a Jenkins server either on-premises or in the cloud. You can use a virtual machine in AWS, Google Cloud, or Microsoft Azure to host Jenkins. 2. Configure Jenkins: Install necessary plugins for integrating with your cloud services. For example, if you are deploying to AWS, you might need the AWS CodeDeploy plugin. 3. Set up Source Control: Connect Jenkins to your source code repository (e.g., GitHub, Bitbucket, or Azure DevOps) to pull the code for building and deployment. 4. Create a Build Job: Create a Jenkins job that pulls the source code from the repository, compiles/builds the code, and runs any tests. 5. Set up Deployment: Use Jenkins to trigger the deployment to your cloud environment. This could involve deploying to AWS Elastic Beanstalk, Google App Engine, or Azure App Service, depending on your cloud provider. 6. Implement Continuous Integration: Configure Jenkins to automatically trigger the build job whenever new code is pushed to the repository. 7. Implement Continuous Deployment: Set up Jenkins to automatically deploy the application to the cloud environment after a successful build. 8. Monitor and Notifications: Integrate monitoring and notifications into the pipeline to alert the team of any issues during the build or deployment process. 9. Security and Access Control: Ensure that the CI/CD pipeline is secure by implementing appropriate access controls and permissions. 10. Testing: Integrate automated testing into the pipeline to ensure that the application functions as expected after deployment. Remember to customize these steps based on your specific cloud provider and the technologies you are using for your application. Additionally, consider using infrastructure as code tools like AWS CloudFormation, Google Cloud Deployment Manager, or Azure Resource Manager templates to define and provision your cloud resources as part of the deployment process.