Walter Buggenhout Community Champion

Hi @Joshua Upadhyay, Given your use case and it seems you are on the server platform, you could have a look at the better content archiving app.. It does provide insights into your content and on top of that helps you in the archiving process itself. Hope this helps! 

Hi @abbas baman, When you change the status to Awaiting testing, there is most likely a post function in your workflow that automatically sets the resolution to Workaround. Edit your workflow and remove that post function. That should do the trick. 

Hi @Samuel Carnall, A wild but educated guess: transitioning issues to different statuses usually means changing the workflow of your issues. It is those workflow statuses that are mapped to the columns of your scrum or kanban boards. When you changes workflows, the status mappings behind your boards do not update…

Hi @Tali.Bartal, Welcome to the community! Something along these lines may help: fixVersion = "X" AND fixVersion was not "X" BEFORE startOfMonth() In this example we're looking at all issues that have been assigned to version X after the start of the current month. Hope this helps!

Oh my - after all these years I just found out I had to click ask a question to create a discussion 🥳

That's interesting @Monique vdB - I couldn't find a link to post in the new to Jira collection, so added the tag new-to-jira manually while creating the post. Is there any direct way to access the New to Jira collection? The way I landed there was by going through the Jira product group and then selecting New to Jira from…

Hi @Michael Green, Yes, so it seems. However, although you can use dashboards with JSM projects, many of the gadgets in there were originally built for Jira Software, where statistics usually support structured custom fields like select lists, radio buttons, labels, components - those things. Organizations is a JSM custom…

Hi @[deleted], The CSAT notification is sent when a request is resolved. Although JSM documentation is not really clear, this is related to status in Jira, but when a resolution is added to a ticket. So exactly as you explain it. To add to that, maybe it is also related to the issue resolved event thrown by your workflow,…

Hi @Rizky.Tuasikal, You have indeed indentified a problem that is caused by a conflict in the standard syntax of MDX used in EazyBI on one side and your status naming in Jira. Those brackets have a function in MDX and you seem to break those with your naming convention. An easy fix would be to update the name of your…

Hi @Philippe LENGLET, Welcome to the Community. Maybe it is not a 100% much, but there is a focused industry group on the Community around Research and Healthcare. Maybe it is a good starting point to join that one and connect there. Also, Atlassian's big Team '21 is just around the corner. That may also be a great…

Welcome to the Community, @Matthew McDonagh! 

Hi @Mohamed Orikat, Welcome to the Community! You are making an entry with a very interesting, but also very extensive question! I don't think there is something like "the reference project". In between the lines of your question, I also hear you rightfully go beyond just configuring the tool, but wonder how you can best…

I am always looking forward to the keynotes. That's were usually a concise overview of all the big news and the important announcements take place. Apart from that, even though it is still a remote event, I am hoping to see many familiar faces and get the chance to (re)connect with a lot of folks I haven't seen or spoken…

@Leah Brindley, I would assume this JQL would return all tickets with linked Zendesk tickets: Project = <your project> AND "Zendesk Support" Is Not EMPTY You can add ordering, but you should also be able to just add the Zendesk Support column to the view in issue navigator and click on the column title to rank them. Hope…

Hi @Pallavi Patnaik, This is because you are not setting a value in the resolution field when you move tickets to that status. When there is no resolution on a ticket, Jira considers those as open issues and because of that still shows them in your backlog. Make sure that in your workflow you set a resolution automatically…

In the general configuration of JSM (<yoursite>.atlassian.net/secure/admin/SDConfiguration.jspa) there is exactly the setting you are looking for: The only thing you'll need to take care of, is that all your users are indeed associated with that one organization.

Hi @Veronica Brits, You can't fix the behaviour you see, unfortunately. The reason for what happens is that an issue exists only once, it is stored in one single project and it has one single status. If you update that status (which is what you are doing by dragging it to a different column on a board), this is reflected…

Hi @Ian Holtham, I don't think what you are trying to achieve is possible. Unless all created tickets are associated with the same organization and all your users who create tickets belong to that organization. The portal is designed to show tickets to external, unlicensed users. They can only see: * tickets they created…

Well, the remaining estimate must have been updated at some point by someone. You should be able to find an update in the history of your ticket. Something like this: But maybe even more important: you can fix this by clicking on the time tracking indicator where we initially saw the cause of the problem. A small dialog…

Hi @CHESTER RAMOS, Atlassian just announced the acquisition of Thinktilt, the company that built Proforma. It will probably take some time before that will lead to a fully integrated solution in the tool, but you make expect a lot of dynamic forms funtionality and easy design to come in the near to mid-term future. Having…

Hi @MIchael Deken, The only differences I can see with my instance are these: * your UI seems to be in Russian, but I cannot imagine that to be relevant ;-) * from the dates on your roadmap, it seems this is a very old one. Maybe your page is not converted to the new page editor yet (I would still be surprised if that…

What columns are you referring to? Can you share a screenshot and clearly point out what you want to change?

@Robert Finkbeiner, Glad too see the validator worked for your create transition. To add to your question about different workflows per issue type: that is exactly what workflow schemes are designed for. You can create a separate workflow per issue type first (that allows you to apply the validator only in your story…

Hi @Tom Emerson, What you describe seems to point very much towards permissions, if you ask me. You need browse project permission in those projects in order to see the issues, as well ass product access to Jira Software. The first is part of project permissions, the second is part of site admin settings (user management).…

Hi @Beth Schwartz and welcome to the community, The tool may not have the formal reports like the previous live plans had. But there is definitely reporting available and the tool has a lot of options available to cover your need to communicate status. When the end of support for live plans was announced, this came with…

That cassette tape was exactly the first thing that jumped into my mind as well :-)

Welcome to the Community, @Sheila Crean! 

Welcome to the Community, @Akhilesh Nawade! 

Hi @Kasturee, Does the user have edit issues permission? Ranking requires an update to the issue in the background. 

Hi @Rajesh Ravisankar, I think you can come a long way with the two dimensional issue statistics gadget. The gadget will require you to provide a filter with the source issues you want to display. Suppose all your issues are in project Demo, use something like: Project = Demo AND issuetype in StandardIssueTypes() and…