Dick Community Champion

I've driven only right side of the road. What keeps me from driving on the left hand side is my fear that all my reflexes to avoid accidents will be completely wrong. So I'm protecting myself (and others!) by refraining from driving in countries where people agree to drive on the left-hand side of the road. yeah, I…

Meet Torve, my young Old German Shepard. He loves taking long walks in the woods nearby. He's always up for finding his "misper" (missing person) when we practice man-trailing. I may assist :)

I'm under the impression that you can/should be able to make a complete workflow. That includes making/adjusting a Workflow Scheme for you entire project (meaning that you get to configure the workflow for all issue types that are available in your project. You do so inside the workflow scheme that is linked to your…

Your workflow Scheme can discern between issue types. Have you looked that up?

Hi @Fabio Racobaldo _Catworkx_ The "+x tickets" have one or more previous sprint names in their sprint field. As currently they do not appear in a sprint, it says the most recent value (none) but also indicate that other value(s) exist (the +1). Only when you correct the content of the sprint field, the +1 will disappear.…

Hi @Jens Bode The lightning symbols represent actions (as per your top picture). I'm not seeing these symbols in the lower part of your workflow (which doesn't seem to have the Implementierung action from your top picture, which confuses me). I take it the top two pictures are the new interface where the actions are…

Tag @Jens Bode In order to make a good working workflow, you need to discern between the status and the action that brings a ticket from a status to another status. In your case the action has no name defined. In the version of Jira I'm running, the name of the action is one of the property-value pairs associated with the…

Hi @Viktoria Gassner Using automation, you can fill the assignee field (hence assign a task to a person). In order to put the right person to the correct epic, you have to include the logic to do so inside the automation. This can be done with a couple of condition lines in the automation. As an alternative, you can use…

Thanks @Bill Sheboy for the addition of the documentation. You really put the cherry on top :) Dick

Hi @sravani vennapusa It would help if you elaborated a bit regarding your problem. This community is geared to answering questions regarding problems you might encounter. It is common to describe your line of thought, including the things you already have tried (but didn't work for you). We rather provide you with a…

Hi @Rashmi Ratnani In the retrospective, agile teams iteratively learn to estimate story points by comparing the complexity and size of stories to stories of similar work that were done in earlier sprints. This process is different for each team. There is no "story point normalization" between teams. So 100 story points…

Hi @GT Welcome to the Atlassian Community What you are experiencing with these special diacritics is that the corresponding utf-16 code of those characters is way higher than the code for Z. Hence the mixed-up alphabetical order you are experiencing. Kind regards, Dick

Above is the standard, no frills configuration of a kanban board. Notice the bottom two entries: * The Kanban sub-filter, kicking out and filled/released fixVersion items * The Hide completed 2 weeks kicking out completed items based on age These filters only apply on board/backlog combo's, not if the exact filter query is…

The point is: if they have a fix/version or release, they do not show up on the backlog, as that is filtered in by the corresponding board you're using.

Do any of the missing tickets have a fix/version perhaps? That would prevent them from turning up on the board and its relating backlog. Kind regards, Dick

Hi @aik8kor That page you refer to, has an explicit mention of a dedicated support channel. I would suggest you use that channel to get the best possible answer to you question. Kind regards, Dick

Hi @Dieter Guthmann From 2023 onward, Jira Cloud allows setting watchers on creation of a ticket. Information on this (and usage) is given in this Atlassian Page. I just found out that this has been taken up in the datacenter 10.3 LTS version of Jira. Good tidings! Kind regards, Dick

Hi @Dhaval Gogate Welcome to the Atlassian Community First of all: a board is not a project. Look at a board as a pair of glasses that can be used to look at a project, at projects or even at parts of projects. Second: Kanban boards don't show released tickets in general (additional board filter in the…

Hi @TK Welcome to the Atlassian Community There's a couple of things you can check: * You should check your board filter. Is it filtering in all your issues? Go to Board - Configuration - General, then edit your filter * Are you looking for your epics in the right place (backlog and board are not the same)? Epics can…

Hi @aik8kor welcome to the Atlassian Community This community forum is the place to receive answers to regular Jira user questions. The answers written here are from fellow user enthusiasts. To me, your question seems pretty high-level, digging deep into the computer code that defines Jira, as you require a guideline that…

Hi @尾崎　洸人 Welcome to the Atlassian Community Subtasks need a parent. As Jira cannot create the parent when you're creating a sub-task, so you need to create the parent first, then from the parent, you create the subtask. Kind regards Dick

Hi @Tatiana Marti This is very much possible. * for last comment: see This Atlassian Page: {{issue.comments.last.body}} * for old status and new status: see This other Atlassian Page: old: {{#changelog.status}}{{fromString}}{{/}} new: {{#changelog.status}}{{toString}}{{/}} Don't forget to close the list iterations with…

Let Cupid's arrows pop all the individual bubbles around the world! Sharing and caring has never been more important. Kudos @PJ Zaiac , huzzah!

Guten Tag @NGO , Your problem description seems a bit unclear, which is partly due to the strange dependance structure you have between the object and the overview form. * Standort Dalt*** seems to be needed to be linked to the Name field rather than the Ort field, which leads me to believe that I am missing some…

Know that boards are not projects. They are merely a pair of glasses that is used to focus on the issues of (parts of) project(s). Kind regards, Dick

Hi @Davide Barri Yes there is, but you need adminship to change it. In the permission scheme used by the project, you can disable extended project management. (it's a tickmark). I had to do this too, as each project admin was inventing his/her own statuses / workflows, which prevented cross-project understanding of the…

Hi @STEPHANIE PENLAND Welcome to the Atlassian Community There's a couple of possibilities here: * 4 stories were completed for over 2 weeks ago (the standard "Hide completed issues older than 2 weeks" filter on Kanban boards) * 4 stories were done and released, thus removing them from the board * 4 non-stories (epic,…

What if one subtask is ahead and the remainder is all on one status? Could you be "saved" by looking up the status of the task that is least progressed in the order of statuses in your project ? Said order should be "known" in the automation. That would require a totally different approach from your original plan. Kind…

Hi @Armando Calvache To be certain, can you open the filter, copy the jql and put that in your action for the lookupIssues ? Then use the validate query button, it should get some results :) Also, you can use the first formula I gave inside a log Action automation step, then visit the audit log to verify its content. Kind…

Hi @Thong Tony Welcome to the Atlassian Community I googled you query and an Atlassian help page came up It specifically refers to the problem being caused by a plugin that wants to use older parts of Jira. There are specific instructions on how to (test before) updates. Best to start there. Kind regards Dick