Bill Sheboy Expert

Hi @Patrik Sulik Your Jira admin can help with this one, by editing your workflow to the Done status and adding jira.permission.work.denied Here is the how-to documentation on this: https://confluence.atlassian.com/jirakb/how-to-restrict-log-work-on-a-specific-status-834225982.html Best regards, Bill

Hi @Sebastian Mühleis I saw another question from a community member on this, and a posted response from Atlassian here: https://community.atlassian.com/t5/Jira-Software-questions/trusted-users-in-my-user-list/qaq-p/1288978 Best regards, Bill

Hi @Saurabh -- Welcome to the Atlassian Community! This is not as easy as it should be with Jira. JQL is not actually SQL... There are marketplace add-ons which could help do this. A work-around without an add-on would be to add a custom-field which is populated from either the Key for an epic or the Epic Link for a story.…

Hi @Peter Wilding I do not know how to solve this issue (without marketplace add-ons), but I found this open "suggestion" on the editor differences. Note that other people have submitted this as a defect rather than a change idea. https://jira.atlassian.com/browse/JRACLOUD-71890 Best regards, Bill

Hi @Shoji Kiriyama You may also consider asking your admin to try the Notification Helper, which can guide them through identifying and correcting issues. Please see here for more information: https://confluence.atlassian.com/adminjiracloud/jira-admin-helper-818578850.html Best regards, Bill

Hi @Jennifer Meyer -- Welcome to the Atlassian Community! Your first two ideas seem like suggestions to improve Jira. Please consider searching the backlog to see if they have already been suggested, or to add a new suggestion:…

Yes, you would need different workflows by issue type because you want the field to be mandatory (and use the validator) for only one type: user stories. Although in all other things you could make the workflows identical, and so making board configuration easier.

Hi @Dean Del Ponte -- Welcome to the Atlassian Community! I believe that you can do that using workflow validators. Please see this documentation for more information: https://confluence.atlassian.com/adminjiracloud/advanced-workflow-configuration-776636620.html#Advancedworkflowconfiguration-validators Best regards, Bill

Thanks, and sorry that I could not be of more help. I suggest pinging Atlassian support as this may just be a syntax issue that is missing from the documentation (or a defect), and after a few searches I could not find examples to help you.

Hmmm... Yes, if you use the email id alone this should work. For your example of an email address of a.b@example.com http://domain.atlassian.net/rest/api/2/user?username=a.b You can rapidly test this with your own email address versus user name. The query string is just the same for both, as you noted. If the email…

Hi @Umesh Kumar and Welcome to the Atlassian Community! @Nir Haimov is correct about the search, and here is the documentation on that API call: https://docs.atlassian.com/software/jira/docs/api/REST/8.5.4/#api/2/user-getUser Best regards, Bill

I just searched the Atlassian backlog and did not see a similar defect, open or closed. What may help you is to write a defect for their support to investigate. They can probably diagnose this better using your specific example and data: https://support.atlassian.com/

Hi @Ryan_Brown I do not think there is a way to remove outliers (or entry errors) with out-of-the-box, Jira. That would be a good addition for some teams. As a work-around, you could adjust the board filter to explicitly ignore the specific story key. The main board filter is used to manage reports, so this would remove…

Hi @Aki Martiskainen Did you notice in your status mapping that some of the status category types (To Do, In Progress, and Completed) do not match the columns on the board? You can see that from the color coding: To Do is gray, In Progress is blue, and Completed is green. The left-most column should be To Do status values…

Ah... It could also be related to permissions of the filters for the respective boards. Have you checked that?

One more thing to try regarding permissions: ask your system admin to try the permission helper to see if it can auto-magically diagnose what is happening. Here's some info about it if you have not used it before. https://confluence.atlassian.com/adminjiracloud/jira-admin-helper-818578850.html

Hi... A board is a view of issues using a filter, which can include one or many projects. A workflow indicates the possible status paths for an issue type. So, as long as one board (for multiple projects) maps all included status values in the workflows, it should be okay. There should be no need to change the original…

Hi @Robert Achmann What have you tried so far? I am asking because I would think this would work as long as you treat the shared board as a read-only Kanban board and make no changes to the issues on it. Maybe try this: * Create a Kanban board with a filter to span your desired projects * Create columns to roll-up the…

Hi @Jennifer_Molyneaux You are correct that this cannot be done with standard Jira JQL queries. I run into this same situation when exporting information to provide more advanced reporting than is available in out-of-the-box Jira. Here is what I do: * Export my child project data (stories, bugs, tasks), including the epic…

Hi @lakshay.batra -- Welcome to the Atlassian Community! One potential cause for this issue is that an issue in the sprint is no longer included in the board's filter, and so the sprint cannot display. To check that, * Navigate to issues and filters and search for your closed sprint, noting the issues in it * Using your…

Hi @kyle I am curious: what problem are you trying to solve by tracking work burn down by individual? If the people are working together as a team, with shared work and responsibilities, tracking work for the team seems better. Having people focus only on their work progress could lead to dysfunctions where people feel…

Hello, again. The color does show in the backlog, and unfortunately the color bars are smaller on the backlog view. If that is not visible enough, you could instead use a quick filter to limit the view of the backlog to just blocked (or not blocked) issues. For example, if during planning you wanted to focus on non-blocked…

Hi @Arianne Lopez -- Welcome to the Atlassian Community! According the the "what's in the works" for the Next Gen public roadmap, time estimates will be added some time in 2020. https://www.atlassian.com/software/jira/whats-new/next-gen#intheworks Best regards, Bill

Hi @M Vijay Kumar How about card colors to see when something is blocked? Then team members can discuss/decide how to proceed rather than having the tool just prevent adding a story to a sprint. You could create a quick filter, as below, and use it to add a card color: issuelinktype IN ("is blocked by") Best regards, Bill

Hi @kyle_bryceland -- Welcome to the Atlassian Community! Have you tried the bulk change feature? You can either select multiple items from backlog and right-click, or create a filter for your issues to change and then select bulk change. If you use the Move option you can change the issue types. Here is some information…

Hi @Dayanand -- Welcome to the Atlassian Community! That is not currently possible, although I recall seeing a post about using marketplace add-on scripting to do so. There is an open suggestion to add this capability, which you can view and consider voting for here: https://jira.atlassian.com/browse/JRASERVER-67721 Best…

Hi @jfuentes -- Welcome to the Atlassian Community! To me, this sounds more like a process issue than a tooling issue. How does your team normally "intake" new work requests? There may be a gap where the product owner/champion is not effectively communicating with stakeholders what is needed to evaluate requests.…

I am not familiar with a History issue type. Where are you seeing that? For the other issue types, such as Task, I think that story point is available. If you are not seeing it, please have your system admin check the field scheme to make it available. It could also be missing from the specific screen scheme. Your…

@Dennis_H -- I'm out of ideas on this one. Hopefully someone else who sees this can pitch in. __Bill

Ah, let's try this. When you look at the attachment, note there is a document-looking graphic in the middle of a white background. Right-click on the document-looking graphic rather than the background. When I do that, I see a different right-click context menu than when I right-click on the white background.