Walter Buggenhout Community Champion

Have a look at the parallel sprints feature for this.

Duplicate of this question.

Hi @Glynnis Kearney, Portfolio needs some kind of estimation or scheduling mechanism in order to calculate the schedule and demand. If you have some (or all) items in your plan unestimated, you can use one of the following methods to work around that: * use default estimates for the story / epic / initiative levels * use…

@Michael Green, Request Participants, like organizations, are specific to Jira Service Desk. There is an additional layer to service desk notifications that you can find inside your Service Desk settings. More on this layer: * Managing Service Desk Notifications (Server) * Managing Service Desk notifications (Cloud)…

Hi @Amrita Nair, There's a couple of things about your request here. To answer your question first: if you are logged in with jira administrator permission, navigate to the Custom Fields administration section (Admin / issues / custom fields) and locate your Platform custom field. Click the cog icon at the right hand site…

Hi @Arianna Celia Frenes Padilla, I am quite sure this is not the answer you want to hear, but I'm afraid this accident will be one you will be telling later on as one of those stories where you sc**d up, but learnt from. The only way to fix it would be through a database restore prior to the moment you deleted the sprint.…

Hi @JiraYo, Notifications in Jira are event-based. The set of events is quite extensive triggering notifications is very extensive, as you can read in this section of Atlassian documentation on notification schemes. As you may find from that read, notifications are triggered from either events on an issue or from workflow…

Hi @Christina Zhanko, When you perform a search in issue navigator, adding the column Work ratio gives you a clear indication of where you are on each task. It is a relative measure though (in %), not an exact calculation. But maybe that covers your main need.

It's a field you can use as a pointer to external information about the project. It is commonly used to point to the related project related documentation in Confluence e.g.

Hi @Luciana Di Matteo, I can see them. They are not in the Backlog, but in To do. If you expand the "to do", you will see them in the backlog view. If you want issues off your to do column and in the backlog, you should be able to drag them there from 'to do'. If you can't, that is probably because there is no valid status…

Hi @Melanie Albrecht, To take away the uncertainty that you have, I would recommend you to contact a Solutions Partner nearby, talk through your ideas and see how they can help you. As from there, you will know where you are at and are still entirely free to take the next step. As you rightfully point out, you should…

Hi @Michael Green, Participants get the same notifications as the reporter of the ticket. See Atlassian documentation for more context.

Hi @Ryan L, For your first requirement, you are perfectly fine with Jira Service Desk. The basics of your second requirement can be covered with Jira custom fields (select list - cascading). With Extension for Jira Service Desk you can build the cascading dynamic forms you are referring to. If you want more flexibility in…

Hi @Mboiteux, The minimal privilege is extended project administration. However, that is only the case if a set of conditions is met: (excerpt from Atlassian documentation) If those conditions are not met, only a Jira Administrator can change the workflow.

Did you commit the releases to the various Jira projects from your Portfolio plan? They only get into Jira after you commit your changes:

Unfortunately not, as far as I know. The only Portfolio for Jira custom fields that are available in Jira are the Team and Parent Link fields.

Did you have tickets in your Service Desk that were closed before you configured the SLA? Another possible cause is that some were closed already before you introduced the SLA. And SLA only gets (re)calculated for open issues.

Hi @Stephanie McCargar, Have a look at the Capacity Report in Portfolio for this.

Apparently something new in Cloud since February 2018. Thx for pointing that out, @Manon Soubies-Camy!

If your aim is to support your user, probably the best way to provide this functionality is through the quick filters associated with your board. Each board automatically has a filter Only my issues. When clicked, the board will only show the issues where the logged in user is the assignee. If you want to group issues by…

Hi @Eric Vormelker, The ability to create project IS restricted to Jira Administrators. It seems that your the users you mention have administrator permissions while they probably shouldn't.

Duplicate of this question

I would recommend you manage this through Tempo Accounts (which come included with Tempo Timesheets). Each account can be assigned an account category (see Tempo documentation). Create 2 accounts for your project; 1 billable and 1 non billable. Make sure to expose the account field on your issue screens, so you have 1…

Hi @Sandra Meessen, No, that is not possible. If you remove an issue type from an issue type scheme, you will be asked to move the related issues to a new issue type:

Both the announcement banner and introduction header allow you to insert links. It is not a button, but it is a link you can add. Just type between square brackets: [Link to…

Ah, that won't work I'm afraid. Typing a number in the quick search fetches the issue key, as you observed. You can - to a limited extent - use basic search in issue navigator. But depending on what you are searching for, this might not give you the most relevant results. On a side note; if you are using Jira as a tool for…

Hi @Jonathan Smith, I am not sure what you are trying to achieve, but if you want to search for specific values in numeric fields, just use the advanced search in issue navigator and specify the field you want to search through. Some examples: "Story Points" = 1 "Story Points" >= 5 Description ~ 1

Hi @Matt Stephens, If you remove the sprint field (by editing the issue), the issue is moved to the top of the backlog. If you have incomplete issues at the end of a sprint, Jira lets you decide where you want to move them: to the top of the backlog or to an open, future sprint that already was created on the board.

I just created a sample report in Jira Cloud for you based on (really basic) sample data: As you can see, issues removed from sprint are clearly listed in the report. Just to make that point visible. But coming back to my previous point on the reason why the team would like to remove a story from the sprint; not having…

Hi @Matt Stephens, This is more a discussion about practice than just about the tool. But a few of my thoughts on this: * Keeping the story in or removing it does not affect what you call your 'true velocity'. Velocity is the number of issue types completed in a sprint. No more, no less. Your original commitment is nice to…