Walter Buggenhout Community Champion

Hi @Tiziana Pisenti, You will only see the epics from parents in company-managed Jira projects you have access to. So, if you only work in a single Jira project, having your permissions on any other projects removed should result in the situation you describe. There are scenarios where it could make sense to link child…

Hi @Agné Smith and welcome to the Community! I don't think there's currently any way to be more specific here. The delivery status represents the status category of issues, rather than the actual status. To go into detail - assuming that your stakeholders have access to Jira - you could share your delivery roadmap from…

Hi @Sandy Hsieh, You did add a column to your board, but you did not add a status to the workflow(s) your project is using. As you can see in the other columns, there is an actual status mapped to each column. Two side notes: * It would be better to map the Won't Do status to the same column as Done. Your board will…

What do you mean by not available from scrum boards, @Shefali Tayade It is true that sub-tasks can only be created from within their parent issue. Just click add and then select Create subtask: Hope this helps!

Hi @이상명 and welcome to the Community! The procedure to cancel a subscription is described in this support article. To be able to do this, you need to be (or be able to locate) a billing admin or organization administrator for your site. If the person who left the company was the only one with that role, you should contact…

Hi @Siva Gnanaparan and welcome to the Community! The sprint and burndown charts display who closed a sprint, but not who started it. So, if a sprint was not closed, there's no immediate way inside the tool to see who did not do this. I would assume there's not so many people on your team who could have forgotten to close…

Hi @Josh Noren, Notifications (in a notification scheme) respond to events. These events are triggered by a post function in a workflow (at least, in company managed projects). If you look into your workflow transitions and select the post functions of a transition, you should see this reflected a the very last post…

Hi @Tong Pham and welcome to the Community! I would recommend you to remove the epic link field from your screens. It has been replaced by the parent field quite some time ago and does no longer have a function. I quite agree that having both fields visible may be quite confusing, but rather than updating the field, I…

Hi @muhammad zahid and welcome to the Community! That is absolutely correct 😃 - do you also have a question or something you would like to discuss?

Hi @Davide Orbitello, Trying to take this step by step. Have a good look at my assumptions along the way to make sure I understand correctly what you are trying to do. So with my automation I'm trying to check if the two summaries match, and if so make the older ticket transition to the same status "DONE" as the last…

Great initiative, this @Sherif Mansour. Very much looking forward to the launch of Rovo pretty soon now (I suspect 😛) 

Hi @Matthew Morris and welcome to the Community! Jira cloud's editor has evolved quite a while ago and does not support markdown anymore the way it did in the old editor and on the server platform. There is a (long standing) request to bring back this capability that you can track here: JRACLOUD-72631 For the specific…

If I take a good look at your board, your rejected status is not in the rightmost column, is it? I see it in unmapped statuses on the left hand side. Also: I did not say you should remove the Done status from your rightmost column. That is exactly where it should be to consider issues as done when you complete a sprint.…

Hi @Frederik Vanhaelst and welcome to the Community! In step 2, don't forget to click the Add button after you select all project roles from a project. Click save after that. Hope this helps!

Hi @Andrey Ivanov, Are your done / rejected statuses mapped to the rightmost column of your board? This is usually the root cause when this happens. Hope this helps! 

Hi @[deleted] and welcome to the Community! This is a scenario that pops up ever more frequently. You cannot simply make the work of both different instances visible as if they were one, but there are several solutions out there that allow you to sync corresponding issues across, so updates on one end reflect in the other.…

Hi @Adam.Cole and welcome to the Community! No, that is not possible. Estimations present the actual work or effort needed to complete a task, while the duration is based on the start and end dates. These are different things, not linked together. Approaching these two concepts have the benefit that you can link estimated…

That should not be a problem. From this support article on how to revoke access: 

I haven't run into this scenario in practice, to be perfectly honest, but from support documentation, portal-only customer accounts should be on the customers list of your project (see last sentence):

Hi @Pavel Kolmagortsev, Why can't you remove the person from customers in your project? In Project Settings > People look for the person and disconnect his account from the Service Desk Customer role. This does your require that your project is not publicly available, so only accessible for people you assign to it. If it…

For further reference (since the feature is not discontinued, as far as I know): https://support.atlassian.com/jira-software-cloud/docs/create-a-cross-project-release-in-advanced-roadmaps/

Hi @anisha, I have the impression that I've seen this question before somewhere, indeed. Cross-project releases are a feature from Plans (advanced roadmaps), available in Jira Cloud Premium. So you need a premium plan to use the feature, which is also only available within the Plans UI. You can't use it across multiple…

Hi @Kamran Ansari, JQL and Dashboards are not features of Jira Service Management. However, to query data and manage dashboards, users do need a Jira license. If you have Jira Software installed in your instance, users should be able to create filters and configure dashboards (even from JSM issues) when they have a Jira…

Hi @Khiry Marchman and welcome to the Community! Since that is a very broad request, probably going way beyond a Q&A in the online Community here, I can warmly recommend you to have a look if there is a local Community Group in your area. They come together regularly and do exactly what you ask for: share knowledge, get…

Hi @Frosty Meyer, I had never really thought about this as I usually define my own version of the gadget, more or less the way you describe. But I just added the gadget to a dashboard, finding out that the default filter behind this gadget is this: assignee = currentUser() AND statusCategory != 3 ORDER BY priority DESC,…

Hi @alipson and welcome to the Community! No, non-admin users don't have access to project settings, where this information resides. I would recommend to provide a documentation page in an accessible place where people can check what role should be selected in a specific case. On a side note, this sounds like a situation…

Hi @antonio coelho silva and welcome to the Community! This looks a bit like a feature request? I don't think it is something that Atlassian is likely to implement, though you can always try to suggest it, e.g. via the in product give feedback option. As an additional tip, though: you can move issues to the top of your…

Hi @Tomas Sugrue and welcome to the Community! Could you be a bit more specific about what you are trying to do and where you are trying to do it? Happy to help, but I am afraid I don't really understand your request in full.

Hi @Andrea Marchesini and welcome to the Community! My first advice would be: don't do that. Communicate with your users and make working agreements about who does what. Jira keeps track of all changes to issues, so if someone does change something he/she actually shouldn't, you will be able to trace that from the issue's…

Hi @Matteo Pacenti, If you want to be notified when the transition happens, then you should simply use an issue transitioned trigger for your automation rule, and then send the notification for that specific issue immediately. That would remove your entire complexity. There is no way to filter for the latest transition,…