Let a slack app create slash commands for another app? (Custom -> Jira)

I am trying to automatically create a ticket every month in Jira. Jira has a slash command to create tickets, which I could use each month to create a ticket myself, but that would not be different than going to Jira and doing it myself.

I would like to have my custom slackbot send these slash commands on my behalf.

Problems so far:
I can’t seem to get the bot to activate a slash command even if it types something with a slash in it.
Jira slash command opens a modal to get more information, so it’s not just “/Jira create detailsdetailsdetails

Any other solutions to recurring tickets for Jira that doesn’t require a paid plugin are welcome as well.

How Can I Freely Export Data From Jira To Power Bi?

There is a Power BI content pack for JIRA to perform this function easily, however this application is no longer available. I think that https://marketplace.atlassian.com/apps/1224…mp;tab=overview is an ideal solution for this purpose. This application is helping to maintain and support all the business and developing tasks, to correct mistakes and bugs and to manage all your products, to make calls between the team etc. So, you can get a flexible agile board and an impressive feature list to manage your projects and tasks.

testing – What should be the workflow for test management in JIRA

We are using Jira to track all our tickets and confluence for documentation. We intend to document the test cases covered on Confluence.

Here are a couple requirements:

  1. Consider a development ticket done and ready for release only when all of the relevant test cases have been written and approved
  2. It is usually the case that developer completes his tickets by end of the Sprint along with Unit test cases and QA writes the integration and microservicee2e tests in the backend repo and Application E2E test cases in the ApplicationE2ETests repo in the same sprint or next to one. FE, BE, and ApplicationE2ETests each have their own repository. Backendrepo contains the unit tests, integration tests, and microservicee2e tests.
  3. Not every single development ticket will have the requirement for QA to write additional test cases as some tickets are just minor optimizations and chore that do not essentially change the test cases from the QA.
  4. The CI-CD pipeline is triggered when the feature branch is merged into the develop branch after PR approval.

What should be the workflow here to ensure that all of the test cases(unit, integration, and e2e) are written when the development ticket gets ready for release.

É possível integrar scripts escritos no Selenium IDE ao Jira ou Jekins?

Atualmente tenho escrito scripts de automação usando o selenium IDE, com isso consigo salva-los em uma arquivo com extensão SIDE e após algumas configurações é possível roda-los em um navegador no modo headless e visualizar resultados pelo console, porém atualmente tenho a necessidade de integrar esses scripts ao Jira ou Jekins e infelizmente não obtive resultados satisfatórios em minha pesquisa.

Alguém já fez esse tipo de configuração e poderia me ajudar ?

8 – Can entity references have “types” like links in Jira?

Suppose I have a node that represents a task, or a to-do item:

Node 1: Instructions for building a drivable car

I want to link this node to another node, such as a sub-task of the original node:

Node 2: Instructions for assembling an engine (Sub-task of Node 1)

Now suppose I have another node that is caused by one of my original nodes, but is not a sub-task of it.

Node 3: How to obtain a driver license (required by Node 1)

The entity reference from Nodes 2 to 1 is of type sub-task while the link from 3 to 1 is of type required by (or maybe related to, whatever).

When viewing Node 1, it might be helpful to display a view of referenced nodes, but rather than just showing the nodes, it would be useful to show the relationship type as well:

Items related to "Instructions for building a drivable car":

| Link Type      | Node                                  |
|--------------------------------------------------------|
| Parent Task of | Instructions for assembling an engine |
| Requires       | Getting a driver license              |

Applications such as Jira handle this via link types. Is functionality like this available within the Drupal ecosystem? Alternatively, what would be a logical way of implementing such functionality?

kanban – How to deal with story-cards on a simple issue-board in Jira

I’m currently organizing a software project via Jira on my own. Right now I’m the only one who is developing on that project. However it is possible that more people will join the team in near feature.

Im now wondering how to deal with stories and tasks. I/We don’t using Scrum but a Kanban board with three columns (backlog, in progress, done). There a a lot of epics and tasks to do and I just include a new issue Type named “story”. How would you handle the state of the stories?

For example:
There is a story called “As a user I want to print the document” and a couple of Tasks which are related to that story like “add printing button to UI” for example. When starting a task, I will move the card to the “in progress” column. The Question now: Should I move the story on the board to “in progress” too? Should we display stories on the board in general? It’s feeling a bit like doing redundant organization since I/we have to check the stories every time tasks changed “by hand” (checking “are all related tasks done?” If yes than we have to move the story too). Or should I prevent using the concept of stories in general?

I hope it’s understandable what I’m trying to describe.

jira – “Dev to QA handover” process improvement

I would like to get some help or ideas to solve my problems,
I just join a small company as junior project manager and I faced with 2 challenges sorry for my ignorance but I am new into the agile world.

  1. QA has many tickets in each sprint that appear as “Ready for testing”. Some of them are indeed ready, while others – not at all.
    what can be the possible reasons for tasks to appear in the workflow as ready for QA, when they are actually not?

one of my thoughts is that the task goal isn’t clear and simple which may cause gaps in the terms of “done” within the development to the QA team
Please list other reasons from your experience.

  1. I have been asked by the QA team lead to find a way for his team to recognize and sort out tasks that are not ready. The tool of task management for all teams is JIRA. What could be a possible solution (or solutions?).

I though about Adding news phases in the flow in order to reflect the precise status,
“Ready for Dev” => “In Development” => “Code Review Requested” => “In Code review” => “Ready for Testing” => “In Testing” => Done

Do you have any other solutions ?

versioning – The meaning of “Fix Version” field in Jira, while working in agile, microservices and CI/CD processes

When working on a monolith application in a “waterfall” process, a “Fix Version” field makes a lot of sense.

Say you have the “November 2020” planned release, you can add/plan dozens of relevant bugs and features to that release. Other bugs and features may be planned for the next release of “December 2020” and so on. So the “Fix version” field can have the same value for multiple issues/tickets.

Moving to a microservices architecture, the above process is significantly changed – Each microservice has its own release cycles that are completely independent of other MS. If a development team is responsible for 10 different MS, theoretically, each one of them can and should be released without any coupling to the others.

When we add on top of that a CI/CD process, things get even more volatile:

When each and every commit to the master results in a full automation tests suite and a potential (or de facto) version that can be deployed to staging/production, then every commit has its own “Fix Version”.

Taking it to the Jira world (or any other issue tracking system) the meaning of that is that each and every ticket/issue may have its own “Fix Version”. No more a common value that is shared across many tickets, but a disposable “Fix Version” value that will be used once.

Moreover, when an issue is created, you have no way to know in which build it will end up, as other tasks may finish before or after it.

In Jira, creating a “Fix Version” is manual, making the process of updating and ticket’s “Fix Version” a tedious and error-prone work.

So my questions are:

  • Are the above assumptions correct?
  • Is there a meaning to a “Fix Version” field in an Agile + Microservices + CI/CD environment?
  • How do you handle the “Fix version” challenge?
  • How do you do it in Jira?