Context and motivation. Jira is an established tool for issue tracking, requirements and backlog management. Its popularity has impact on how agile software projects are conceptualized by project team members, often dictated by the data structures being managed within the tool. Question/problem. Although user stories should be traceable to both software artifacts and business processes, both sides being well served by modeling standards (BPMN, UML), the diagrammatic semantics are not leveraged by issue tracking tools; conversely, modeling tools have been more interested in code generation than in supporting issue trackers and agile practices. Principal ideas/results. We propose a diagrammatic alternative to Jira, a modeling tool built around a domain-specific modeling language that integrates Agile Software Project concepts with modeling standards (BPMN, UML), while also ensuring interoperability with Jira. The engineering effort was based on the metamodeling approach known as Agile Modeling Method Engineering. Contribution. The DSML underlying the tool is a conceptual bridge between modeling standards and Jira, and it is developed as a Design Science treatment, iteratively increasing its technological readiness.