Improved Jira notifications - How to customize email template content for email notification
a project by xgonzo
Updated almost 4 years ago. 1 hackers ♥️. 1 follower.

Problem description

Jira is used inside SUSE to track various process/workflows. Notifications for all workflows are using the same standard template.

Objective

  • dig deeper in Jira
  • learn and understand Velocity template engine
  • improve basic Groovy skills
  • implement at least for two different workflows a customized email templates
  • document how to adapt templates
    • start a best practice pages with hints based on my experiences on the first implementations

Join this project

Looking for hackers with the skills:

jira groovy velocity templatemetaprogramming confluence

This project is part of:

Hack Week 19 Hack Week 20

Activity

  • over 4 years ago: xgonzo added keyword "jira" to this project.
  • over 4 years ago: xgonzo added keyword "groovy" to this project.
  • over 4 years ago: xgonzo added keyword "velocity" to this project.
  • over 4 years ago: xgonzo added keyword "templatemetaprogramming" to this project.
  • over 4 years ago: xgonzo added keyword "confluence" to this project.
  • almost 6 years ago: keichwa liked this project.
  • almost 6 years ago: xgonzo started this project.
  • almost 6 years ago: xgonzo originated this project.


    • Comments

    • xgonzo
      over 4 years ago by xgonzo | Reply

      I hope to find time for it in HW20

    Similar Projects

    issuefs: FUSE filesystem representing issues (e.g. JIRA) for the use with AI agents code-assistants by llansky3

    Description

    Creating a FUSE filesystem (issuefs) that mounts issues from various ticketing systems (Github, Jira, Bugzilla, Redmine) as files to your local file system.

    And why this is good idea?

    • User can use favorite command line tools to view and search the tickets from various sources
    • User can use AI agents capabilities from your favorite IDE or cli to ask question about the issues, project or functionality while providing relevant tickets as context without extra work.
    • User can use it during development of the new features when you let the AI agent to jump start the solution. The issuefs will give the AI agent the context (AI agents just read few more files) about the bug or requested features. No need for copying and pasting issues to user prompt or by using extra MCP tools to access the issues. These you can still do but this approach is on purpose different.

    Goals

    1. Add Github issue support
    2. Proof the concept/approach by apply the approach on itself using Github issues for tracking and development of new features
    3. Add support for Bugzilla and Redmine using this approach in the process of doing it. Record a video of it.
    4. Clean-up and test the implementation and create some documentation
    5. Create a blog post about this approach

    Resources

    There is a prototype implementation here. This currently sort of works with JIRA only.

    Review SCC team internal development processes by calmeidadeoliveira

    Description

    Continue with the Hackweek 2024, with focus on reviewing existing processes / ways of working and creating workflows:

    Goals

    • Check all the processes from [1] and [3]
    • move them to confluence [4], make comments, corrections, etc.
    • present the result to the SCC team and ask for reviews

    Resources

    [1] https://github.com/SUSE/scc-docs/blob/master/team/workflow/kanban-process.md [2] https://github.com/SUSE/scc-docs/tree/master/team [3] https://github.com/SUSE/scc-docs/tree/master/team/workflow

    Confluence

    [4] https://confluence.suse.com/spaces/scc/pages/1537703975/Processes+and+ways+of+working