Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Certificate of Excellence - Praveen Soundarrajan 1.0.0


1 Screenshot

About This File

When working at H&M as the Jira expert I issued Certificates of Excellence to the Gods of Jira team. This one was issued to Praveen Soundarrajan for his outstanding work as a Jira expert.

"For performing above and beyond
Awarded for working in a professional way with exceptional dedication
that has been above and beyond just being service minded. It is
also awarded for a positive attitude that is appreciated by
co-workers and clients alike. Finally it is awarded for being
passionate and being active in learning new things in Jira."




User Feedback

Recommended Comments

There are no comments to display.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Add a comment...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By ©Jimi Wikman
      This is a repost from Atlassian's blog where the latest updates to the Atlassian cloud platform is posted. It is reposted here since the Atlassian blog does not have an RSS feed and so we can discuss the changes to the Atlassian Cloud architecture. You can follow these posts withe the tag "atlassian cloud changes".
      Atlassian Cloud
      Your cloud-hosted products are supported by the Atlassian Cloud platform. This section usually includes changes related to multiple Atlassian Cloud products, site administration, and user management.
      Email users with suggested account changes 
      From the Change details button, you can suggest that a user changes their account details to make their profile more consistent and easier to identify. Read more about administering Atlassian accounts.
      Give your users a Trusted permission 
      From a user's Permission options, select Trusted to give certain users more responsibility. These users will be able to install and configure new products on your site and invite new users themselves.
      Claim accounts after verifying a domain 
      To start managing accounts on your domain, we’ve included an additional step that requires you to claim accounts after verifying that you own the domain. From the table on the Domains page, click Claim accounts next to the verified domain. Read more about verifying a domain.
       
      Jira platform
      Changes in this section usually apply to all Jira products. We'll tell you in the change description if something is only for a specific Jira product.
      Next-gen: Epic panel in backlog 
      You can now manage epics on the backlog of your next-gen project via the Epics panel, similar to how epic management works in classic Jira Software projects. Changes you make in the panel on the backlog will reflect on the Roadmap, and vice-versa.
      New issue view: Add web links
      Save time and add context to your issues by adding web links in the new issue view. Web links are links to any URL, but they appear prominently below the issue description where they’re easy for you and other issue viewers to find. Use them to link to important sites that teammates might need to better understand an issue.
      We’re also moving all issue link types, including web links, into the Link issue button. Click Link issue to quickly link related issues or click the down arrow on the button to add links to web pages and Confluence pages (if you have a linked Confluence site).
      Find issues you've recently worked on 
      We’ve added a new Worked on tab to the Your work page. This tab lets you quickly find and resume work on issues you’ve updated recently. Head to Your work > Worked on to get started.
      Improved navigation in Jira Cloud 
      We’ve created an improved navigation experience that always appears at the top of the screen, with clearly labeled buttons and menus to help you search, create, and resume your work. Find out more about our improved navigation experience and when you can try it out.
      New issue view: Improved date formatting in the history feed 
      Dates in the history are now more consistent. They’ll correctly show when changes happened relative to your time zone and be translated into the language you’ve chosen for Jira.
      Prevent cross-project commenting when replying to an email thread
      This release ensures that the comments added to a ticket, sent to the specific project email address, will only appear on the ticket in that project.
      Previous behavior
      Bruce receives an email notification about ticket - ABC-123 from his next-gen project “Facilities” Bruce comments in the body of the email, “This contract needs input from legal” and forwards the email to the next-gen project “Legal”. Bruce’s comments would be added to the ABC-123 ticket in the “Facilities” project.
      New behavior
      Bruce’s email will create a new ticket in the “Legal” project.
      Select your email notifications for issue activity from personal settings 
      Jira sends email notifications when certain activities occur on issues. In your personal settings, you can now choose whether you want these notifications. If you do, you can toggle notifications for issue activity when you’re a watcher, reporter, assignee on an issue, when someone mentions you, and when you make changes to an issue. Learn more about choosing email notifications.
      Issue collector no longer matches the submitter's user session to make them the reporter 
      We’ve adapted our issue collectors to the Chrome browser’s new cookie security features, but have had to change how they work. The issue collector no longer matches a submitter’s user session to make them the reporter. You can still match them by email address.
      To improve issue security, project and issue keys are no longer displayed in the success message after submitting feedback on an issue collector (unless the project is open to anyone on the web).
      Learn more about using the issue collector.
       
      Jira Software
      We're rolling out a new type of project known as next-gen. By default, any Jira Software licensed user can create their own next-gen project. These projects don't affect existing Jira projects, shared configurations, or your schemes. You can manage who's allowed to create next-gen projects with the new Create independent projects global permission. Read more about next-gen projects.
      Next-gen: More epic colors on the roadmap  
      There are now 8 additional colors for your epics on the roadmap. Simply click on an epic to see its details, and select the epic color to view the new options available. Learn more about managing epics on the roadmap.
      GitHub app on the Atlassian Marketplace 
      We've partnered with GitHub to build a new and improved integration, which you can install at the Atlassian Marketplace. This replaces the DVCS connector in Jira's system settings. Current GitHub integrations set up under the old method will continue to work, but new integrations must be set up using the app on the Atlassian Marketplace. We're rolling out this update gradually, so it may not be on your Jira Cloud site yet.
      This won't affect GitHub Enterprise integrations, which must still be set up via the DVCS connector.
      Next-gen: Create child issues on your roadmap 
      You can now add child issues directly on your roadmap. Just hover over an epic, click the + icon, and give your issue a name. Learn more about managing epics on the roadmap.
      Kanban boards just got faster 
      Is your team so productive, their 'Done' column is always overflowing? Too many issues on a board can slow it down and make you scroll way too much. To fix this, we’re bringing what we’ve codenamed “Fast Kanban”—a way to keep your board fresh and clean, and as quick as a flash.
      The idea behind it is simple. The ‘Done’ column will now show only issues that have been updated (in any way) in the last 2 weeks, hiding the rest. Less noise on your board means happier teams. Any project admin can change the retention period, or choose to display all issues, if they prefer. Learn more
      Quickly copy a link to an issue in your next-gen project backlog 
      When viewing your backlog, you can now copy a link to an issue to your clipboard. To try it out:
      Navigate to your next-gen project backlog. Locate the issue you want a link for. Select More (…) > Copy issue link. The link to the issue is copied to your clipboard, ready for you to paste into a Confluence page, Slack message, or anywhere you might want to share your issue’s link.
       
      Jira Service Desk
      New issue view for Jira Service Desk 
      The new issue view groups key actions and information in a logical way, making it easier for you to scan and update requests. Learn more about the new issue view.
      Use keyboard shortcuts in your queues 
      Use keyboard shortcuts to navigate around your queues and get your work done faster. You can now move through issues, select their fields, and go to the issue view from your queues just by using your keyboard!
      Remind agents to update empty fields when moving a request in your next-gen service desk 
      We added another rule to your next-gen service desk workflows. Now, you can prompt your agents to complete an empty field when they use a specific transition to change an issue’s status. The rule removes a burden on your teams to remember to fill in specific fields until they matter. It keeps them focused on the important work of helping your customers.
      To learn more about the rule, and get an example of how to use it, check out our complete documentation on next-gen workflow rules.
      Global create can select request type and raise on behalf of 
      You can now create a request on behalf of your customers and set them as the reporter. Use the global create button ( + ), then select Raise this request on behalf of and add in your customer's email.
       
      Confluence
      Your editing experience just got an upgrade 
      The new Confluence editor allows anyone to create beautiful, powerful pages effortlessly. Check out the editor roadmap to learn more.
      End of support for nested tables 
      As we work on creating a more stable editing experience, we will no longer support nested tables - that is, a table within a list, block quotes, or another table. Existing nested tables will not be affected, you simply won't be able to create new nested tables.
      We're extending editing improvements to all pages on Android 
      The editing improvements we made to blogs a few months ago are coming to the rest of your Android mobile pages, too. In addition to being faster and more reliable, your new pages are also responsive, optimized for readability, and have advanced tables. Some macros are still missing as we rebuild them, but you can check the list of changes and track updates to macros on our docs site.
      Jira issue URLs are converted to smart links 
      When you paste a Jira issue link into a Confluence page, the URL is converted to a smart link that displays the page icon and the page title. This works if the Jira and Confluence sites are linked or if they are both cloud versions.
      Convert pages to use the new editor 
      You can now convert your existing pages that were created using the legacy editor to use the new editing experience! Learn more
      Confluence navigation just got better 
      Get to information faster with improved navigation – making what you need visible from anywhere in Confluence. Learn more
      Portfolio for Jira plan macro 
      The Portfolio for Jira plan Confluence macro lets you embed a Portfolio for Jira Server and Data Center plan in a Confluence page. Join key stakeholders in the spaces where business goals are built and tracked, and share how work is progressing across multiple projects and teams.
       
      Bitbucket
      Pull requests now include a Jira issues panel 
      In the sidebar of the new pull request view, you can now see a list of Jira issues related to this pull request and Jira issues created in this pull request.
      New Code Review - Limit the amount of rendered diff content 
      Limits the amount of pull request content rendered in the diff and file tree to improve browser performance. Limits include the overall number of files and number of lines for the entire diff. Learn more
      Show Jira issues assigned to the current user on dashboard
      You can now see your assigned Jira issues on your Bitbucket work dashboard.
      Recent repo cards on Bitbucket dashboard
      We’ve improved the way you see your recent repositories by adding a new section on your Bitbucket work dashboard.
    • By ©Jimi Wikman
      Priorities
      View File A simple icon set for Priorities I use in my own Jira instance.
      It uses colors to indicate priority / Severity ranging from full red in the blocker and then scale down in the color range down to purple for the lowest.
      The symbols are simplified as well to make them as visible as possible.
      Included:
      Blocker - Full red with a blocked icon as the indicator. Highest - 7 sided background in deep red with a white exclamation mark. High - Orange triangle pointing upwards. Medium - Green circle Low - Blue triangle pointing downwards. Lowest - Three purple dashes. Submitter ©Jimi Wikman Submitted 02/04/2020 Category Graphics  
    • By Praveen S MOD
      I am working on Atlassian applications like Jira, Confluence, Portfolio for Jira, etc. as a tool administrator and process and methods designer. Also have over 4 years of experience as a production support executive.

    • By ©Jimi Wikman
      One of the most common questions I get is when to use the issue type Task in Jira. This is not surprising since Jira is intentionally not defining how to use the issue types and their hierarchy. This is to avoid restricting the users from building a way of working that is best suited for them. In this article I will explain my thoughts from a development perspective.
      As I have described before in the article "Setup Jira and Confluence for success - Part 2: Defining Jira Issue Types" there are three levels in the standard Jira hierarchy. Task would fall into the middle level and the sub-tasks would be the last level. This means that Task would be on the same level as a Story and that is what we can start from when defining what should a Task be for in a development perspective.
      In a normal workflow for development we would have a Story issue created as a result from the requirement, or need if working Agile, process. So the Story would map towards a need or requirement and as such we would have a workflow where we can trace actions from idea all the way to production.

       
      Then where do Task fit into that workflow?
      In most cases it will not as a task would not be a part of a requirement or a need. That is what a Story is for. A Task is most likely only going to be used for Task management rather than as a workflow. This means that a Task would most likely be something that have limited states such as New, In Progress and Closed. It might even just have New and Closed to be even closer to the way task management is defined.
      In a development situation where you need to have a workflow a Task is best suited for activities that are not directly related to the workflow. Things like setting up environments, prepare presentations or Demos and even things like buying cake for the next retrospective (which of course always is mandatory!).
      If you use Tasks in this way, then sub-tasks would follow the same pattern. For a development task for example you might need to schedule a meeting with an external vendor to go over the API details for an integration. For a test task you might need to organize a workshop for end to end testing across multiple teams and systems and so on.
      In short, my definition is that Tasks are used for internal task management that is not directly related to the workflow.
      Do you agree or disagree?
    • By + MilosK
      Miloš is a calm and organized e-commerce developer skilled in Java (especially hybris) and web application development with a strong interest in software engineering, continuous delivery and automation. Miloš is social and quickly adaptive to a new environment or a role. His good analytical and critical thinking helps Miloš to adopt an objective view on a given task. Miloš is focused on details, eager to face new challenges and always strives to help the team with self-improvement and optimization.
×
×
  • Create New...