Walter Buggenhout Community Champion

Yay! Welcome fellow champions :-)!

Hi @Rajesh Ranjan, It seems that the formula column is not available in Structure Cloud yet. Check the https://wiki.almworks.com/display/strcloud/Structure+Cloud+Roadmap for more information. The page also has contact information of the vendor if you'd like to contact them directly. 

Hi @Cheryl Neil, Next-gen does not have the advanced workflow capabilities you need to set up the process you describe. To start with question 5 on your list: Jira Software classic does. Let me introduce a few pointers to get you on the right track there ... Question 1 and 2 can be covered with Jira Software classic…

Hi @Dirk Oesterreich, This change is most likely related to this announcement regarding the upcoming transition to the new issue view. You can find more background information about that view right here. For more instructions on how to enable/disable the new issue view, refer to these instructions. 

Hi @Jordan Lucas , I did a quick simulation of what you describe on a test site and I am seeing the exact same thing as what you describe here. According to the public product roadmap, the feature is currently in the works and is expected to roll out further in Q1 2021: In the meantime, if you would like to embed a roadmap…

Hi @Emil Petersen, Based on this information, it is very hard to diagnose the problem. Just guessing that trying to delete swimlanes means that they are based on JQL queries, maybe the query behind the swimlane you want to delete refers to something that is no longer valid. Before trying to delete the swimlane, have you…

Hi @Otto Tillmann , I suppose you are referring to the Tasks you can insert from the menu bar and that come with a check box? You cannot disable the feature in Confluence Cloud. And probably that is a good thing, looking at the possibilities it may offer as well. Suppose you manage the agenda for meetings in Confluence and…

Hi @Pi Network Support , Yes, there is. Create a new report and then add multiple series, 1 for each request type you want in your report. To do so, create your report first. While you are editing it, click the Add series button in the top right corner. Then, in the dialog specify the type of data for your report (e.g.…

Hi @[deleted] , the answer to your 2 main questions is two times "Yes". Public access is really public access to anyone. And invited users will consume a license. As a workaround for your use case, it might be possible to use Confluence as a CMS and use a publishing app from the marketplace as an extension to expose…

Ok @Shahzad Anjum, I'm not sure if your feedback is related to the initial question by @Ashish Pandey. But based on the screenshot, 2 things: * Maybe the attachments are indeed of an unsupported file type, so they cannot be previewed in the Cloud UI? I can't judge that based on the screenshot itself. If you click the…

To assign multiple issues to the same release, I would recommend you use the backlog view of your scrum board to do so. It is the view where you plan your sprint and where you have a Versions panel on the left of your screen. You can simply drag issues from your backlog on the version of your choice there to assign the…

Hi Robert, The releases are populated based on the Fix Version field instead of affected version. To clarify: for e.g. a bug, the affected version is the version/s of your application that are impacted by the bug. The fix version is the version in which you are releasing the fix for that bug. As one points to the past, the…

Hi @Ashish Pandey, It might be a better idea to use the Jira Software Migration Assistant tool (Marketplace listing ) for this type of operations. It has built-in support for migrating the attachment files (with the projects they are associated with). The tool is free, so no obstacles there - I guess.

Hi @Lynn Ahrens, As until now, comments are indeed only visible in view mode. There is - however - a feature request for that and you can track it here: CONFCLOUD-36956. The good thing is that development of this feature seems to have started and that the option is on its way ...

See the article @elizabeth_jones is referring to. In case you are referring to the administrator's account as a billing/technical contact in My Atlassian, this article may be helpful as well. Should you have problems accessing your company's My Atlassian account, it's best to reach out to Atlassian support directly.

Am I correct that this announcement is also incorporated in Jira Cloud documentation? 

I just spent 15 minutes figuring out how I could update the Epic Status of an epic that was accidentally marked as done by a user. Seems that somehow the new issue view is already forced on the cloud site of this user and that in the new issue view the Epic status field cannot be shown, even though it was on the edit…

Hi @Nancy Ngulube , There's a really good answer to your question right here: https://community.atlassian.com/t5/Jira-Core-questions/Jira-Service-Desk-Agents/qaq-p/1292781. Hope it helps!

Hi @Matthew Canham, Me again. Sorry to keep getting back to the same topic again. I've done some checks and would like to be very specific about my concerns here: The above screenshot comes from a current cloud site. You mentioned earlier that nothing changes with regards to classic project configuration, but screen…

@Matthew Canham , If you plan to make the resolution field editable, I assume it will be possible to disable that as well? Setting the resolution is an essential part of marking an issue as done and should not be set freely at other stages in the workflow.

Thanks for clarifying that, @Matthew Canham. So just to make sure I understand well: the new issue view will only be pushed through in next-gen projects? Or also in classic projects, but with the nuance that there will still be separate issue screens, but displayed with the features of the new issue view as well? 

Hi @Matthew Canham , What is the impact of this change on screen scheme configuration in classic projects, if any?

Thx for the credits, @Priya _View26_ :-)

Hi @mark.phinney, Your assumption is correct. The SLA feature is a Jira Service Desk feature and only available in a Jira Service Desk project. It cannot be enabled in a Classic Business Project (which is Jira Core functionality) unfortunately. If tracking SLA's is what you're after, create a Service Desk project instead.…

To filter for exactly what you describe: status in (open, reopened)

Hi @frederic, Just rerun the import of your plan. Click the cog icon next to your plan's name and select Configure. Then, navigate to issue sources in the left side navigation and click Edit issue sources. Then - depending on how you removed the initiatives from your plan - navigate through the different steps of the…

Hi @Harsha H P, Try the following search: issuetype = bug and timespent is EMPTY and status in (done, closed) and sprint in openSprints() * Where timespent searches for missing worklogs; * sprint in openSprints() searches for the current sprint; * issuetype and status represent what you may expect them to ;-)

Hi @Tran Le, Have a look at the Jira documentation on managing project roles. 

Hi @Nicola J , Does the board contain issues of multiple projects? If so, users must have manage sprint permission on all projects returned by the board filter.

Hi @Nate_Martin, Fields being required in the use case you describe is done through the validators in your workflow. As long as different issue types have their own workflow, you can perfectly make different fields required on different issue types. Have a look at Atlassian documentation | advanced workflow configuration.…