Walter Buggenhout Community Champion

Adding to that: if you are planning to do this on a regular basis, you might be better of implementing Jira Service Management at some point. You don't need to be to grant access to your external users (customers) there and there's much easier communication features there with these external users.

Hi @Akhil Namdev, That all depends to where you stored the email address of the sender when you created the issue originally. You can use smart values in the To field of the send email action in automation, but it requires the email address of that person to be somewhere on your issue. Suppose you have added this in a…

Hi @Martyn Gigg and welcome to the Community! No, not that I know of. The vertical markers you can set on the timeline in Plans (Advanced Roadmaps) are the release dates of the releases in your plan. If you add releases to your plans that correspond with your goals, you can mock what you are trying to achieve, but you…

Hi @Jason Chayer, As long as you have create issues permission in the project you want to move issues into, yes, sure. You may need move issues permission on the read only project too, I would assume. Hope this helps!

Hi @Michael Karl, Check out the Compass pricing and user/role definitions to fully understand pricing. There is a free and a standard plan, with major differences the number of full users and templates you can use. Hope this helps! 

Hi @Amanda Britton and welcome to the Community! First and foremost: no worries about the learning curve; we've all been there and it's not something that is just Jira - stepping out of our comfort zone and learning new things is what makes us better / stronger after all 😉 Diving into your question - I would first of all…

Hi @Nathan Nicholson, This is a scenario I have not experienced yet, but still ... Product Discovery projects under the hood are team managed. That is not an ideal situation for reporting cross project, as things like status, most custom fields, ... are restricted to a single project. Having said that, if there is one…

Hi @Stacey Telford, A few things that you can/should verify: * Plans (advanced roadmaps) does not use the original estimate) to display the estimates in a plan, but it uses remaining estimate instead. Usually, when you add the original estimate to an issue, that value is automatically copied to the remaining estimate field…

Hi @Marcus Hammarberg and welcome to the Community! No, unfortunately not. While you can control which fields are displayed, you don't have control over the placing and look and feel of these additional fields. Hope this helps!

Yes indeed. Because you have some additional marketplace apps in your system, the buttons are collapsed. But it is the same thing 🤗

Hi @David Arévalo, Yes indeed 🤗 - that is correct. Hope this helps! 

Hi @lars, You don't need to do much. Once you have created an issue, just hit the Link issue button at the top of your screen. Then, a section will appear on your issue view where you can add such links. On an additional note: in company managed projects you need to have the link issues permission in order to do this. And…

Hi @Benjamin Buchwald, Even if it were possible, I would not recommend this. Generally speaking, making tools block creating issues usually leads to frustration, misunderstanding and sometimes even the need for complex workarounds when you do want to allow exceptions. Rather than blocking this, you could instead use an…

Just a second, @Arthur Brown - let's not take shortcuts 😛 First of all: it is possible to create a board for one (or even multiple) company managed projects where you map a status to the backlog and other statuses to the board. Thus you can indeed ensure that changing the status of your issues moves them from the backlog…

Hi @Benjamin Barniskis, The external Atlassian Access is not relevant for your use case. The good thing is that your external user already has an Atlassian account, identified by his/her email address. If you want to add that user to your site, you can invite him/her with that email address. If you want to provide that…

As to your comment: Sorry to come back to this. I have added manually to some tickets now the Request Type and added myself as a Request Participant. Afterward, I am able to view the Ticket in the Portal, but still, when I send out a public comment, neither the client nor I get an email. A couple of things you should…

Hi @Stefan Speck, This community article might be worth a read on this topic. It explains how to set up a custom email address for your JSM project. Hope this helps! 

Hi @Lynne Ratcliffe, I am not sure why the capacity would be important for later reporting. If you know your team's capacity for the upcoming sprint, you would add work to your sprint to match that capacity, so you can ideally deliver what you planned for. The velocity chart already delivers a view of what you committed to…

Hi @Aimee Heigold, What is the problem you are trying to solve here? It looks as if you are trying to fetch a list of items to discuss in a review meeting, but with a hard dependency on a date field. Starting from that idea, your examples are pretty much ok. But have you considered solving your process differently? If you…

Hi @Nicodemus, Apart from the fact that I don't see the sprint names at the bottom of the chart and assuming that this is just due to the way the screenshot was taken, here's what I see: * The grey bars represent the number of story points committed (at the start of the sprint). * The green bars represent the number of…

Hi @Jake S, A lot depends on what you mean by incident has been in sprint and then been sent to none When an issue is added to a sprint, that sprint is filled out in the Sprint field on the issue itself. When you complete a sprint, that information stays on the sprint field, even if the issue is no longer there. The None…

Hi @Vera Valshonok, The workflow for a ticket is determined by the issue type being created. In Jira Service Management, each request type is linked to 1 (and only 1) issue type. So, the workflow being used will always be the one that is linked to the issue type associated to the selected request type. So, in your example,…

Hi @alex_borges and welcome to the Community! You can see issues like that because this is Jira Software, not Jira Service Management. If you want to expose issues to the outside world like this, you would need to enable anonymous access to do this without having to pay a fortune on licenses. No need telling you that it is…

Yes @Kamalkumar S_ Chandran, that is a correct observation. As I mentioned, the sprint report has the exact details, but it can only be viewed one sprint at a time. The out-of-the-box gadgets in Jira let you create overviews across multiple sprints, but they have this limitation indeed. To create a nice overview of all…

No, indeed. You cannot use a quick filter to define the sorting of your issues, as I mentioned before in the first comment below my initial reply. Quick filters are filtering issues, not sorting them.

Hi @Christian Hockenberger, Have you filled out the Request Type on the automatically created ticket? If that field isn't filled out, the ticket won't be accessible for portal customers. Hope this helps! 

Hi @Andreas Köhler, Can you add what type of project (team managed or company managed) you are using and what product (Jira Software, Work Management, Service Management or Product Discovery)? 

Hi @David Arévalo, When your order is processed, the update should be immediate. If you are trying to determine how long you can wait before the validity date of your quote, I would still suggest to not wait until the very last second or so to place your order. The same goes if you are purchasing the upgrade via a partner:…

Thx for those screen shots, @Hofit Levy. So you want to see issues by priority in the backlog? My answer remains almost the same - only the swimlanes option is no longer relevant here as they will only be visible in the active sprint view. Assuming you want to use priorities to add the highest priority issues to a sprint…

Hi @Arthur Brown, that is correct. A board in a company managed project is either a scrum board (which allows you to support a scrum team by creating, starting and completing sprints) or a kanban board (which is designed to work without sprints). Unlike in team managed projects, there is no toggle to turn sprints on or…