Walter Buggenhout Community Champion

I understand, but you can't initiate those up front. As a workaround, you could simply reference them in your sprint names, though.

Hi @Simon Phillips, You can add as many (empty) sprints as you like. You cannot set the dates up front, as they are filled out when you start the sprint. But that should not keep you from creating a couple right away. (just click the Create Sprint button a couple of times)

Hi @Emma van de Vreugde, no, that would be sad, wouldn't it? Your free license should grant you access for up to 10 people, but they will all be project administrator in your projects. So they'd rather have too much permissions than too little. 

This may be related to a property associated with the Done status in the workflow. To find out, edit the workflow, select the Done status and click properties. See if there is a property jira.issue.editable with value false. Remove that property if you are sure you want to update this and publish your workflow again. See…

Oops, I noticed you are on the free plan just now. In that case, you won't be able to assign project permissions as per these restrictions. I'd expect a direct link to the project url should do the trick then. 

Hi @Emma van de Vreugde, You should probably also add the participant to one of the roles in the project he is supposed to collaborate on. In your project, go to project settings > People and add him to an appropriate project role there. In case you may have done that already, there may be a chance that he/she is accessing…

Hi @Wansze Kong, One thing you are trying to do is not possible: you cannot hierarchically rank tasks under stories, as they are by design in Jira at the same hierarchy level. The default hierarchy works like this: Epic >> Story / Task / Bug (essentially all issue types that are not Epics and not sub-tasks) >>>> Sub-task…

Hi @JanaW , There are several ways to accomplish this. One way is to implement issue-level security on your project. It basically adds an additional layer of security on your project that allows you to set visibility at issue level. Read more on how to configure this here. An alternative would be to add a user custom field…

Hi @Ollie Whayman, It is currently not possible to block attachments from email requests when creating tickets. There are feature requests suggesting improvements for that: * Be able to remove images in mail body (JSDCLOUD-2090) * Remove e-mail signatures from incoming mail (JSDCLOUD-5878) You can vote for those and watch…

Hi @marcov, JSM will be released with version 4.14. The upgrading process should be the same as with any previous upgrade of JSD in the past. You are most likely aware of the announced end of sales for the server platform, so keep an eye on the JSD Release Notes to see what happens and when.

Hi @OpsGenie Admin , There is no specific configuration required. The only prerequisite may be that the Attachments field is on the create issue screen. As long as that is the case, just hit [CTRL + V] to paste the screenshot. It will automatically be attached to the issue. Don't put your cursor anywhere, just paste.

Hi @Bridget Lamb , Go to Project Settings > Customer Notifications. There you can find various email templates you can adjust. This one is the Request created template.

Hi @Helen Pippard , When you complete the sprint, your open issues will be moved into the location you specify (another sprint or the backlog). Issues that run across multiple sprints will by default be associated with all the sprints they were in. There is different behaviour when you report on issue count vs time spent.…

Hi @Sashidharan, That is a very open question. So I guess the answer is yes. Essentially, you would set up an Atlassian account (which may be private, or managed) and this single account would allow you to access all your Atlassian products. All of them. As there is a lot under the hood here, have a look at this article.…

Hi @Steve Daniel, It still is an open issue indeed. You can track it here: JSWCLOUD-17773 (or use classic projects, where the feature is available) 

Hi @Helen Khamooshi , The link you shared points to Advanced Roadmaps, which is a feature of the Jira Cloud Premium plan. They are not available in the standard plan. The roadmap you have in your standard plan does not have the ability to drill down into subtasks. There is an open issue for it in the backlog that you can…

Hi @Ofira Daniel, It may be me, but it seems there is a contradiction in your question: * you say you want to search for issues from all jira projects in the same sprint * and you add that each project uses 1 active sprint Probably I misunderstand the last bit, because if each project has its own sprint, you could query…

Hi @Marco Van Deventer, That's a creative approach to manage project status :-) I don't see how you could use the update of project category to trigger an email notification, to be honest. That information is more situated in the master data of your project settings rather than in your actual workstreams. A simpler…

Hi @Jonathan, Navigate to Project Settings > Portal Settings. Then select Portal groups and just click on the name of the group you would like to change. You can type and update inline:

 Hi @Port Administrator, I'm afraid you can't customise the color. It screams because the tickets are all significantly overdue. I do notice that the SLA configuration has room for optimisation. E.g. your SLA timer keeps running while the ticket status is Waiting for Customer. Usually in such a status, the timer is being…

Hi @Swaroop, These transition dates are already logged automatically by the system in the issue history. You can see them mentioned under history at the bottom of your issues. It may be an option to surface the information with scripted fields, as you can see explained in this related question.

Hi @Liz Medsker , Great you are in the right place already with this: I think in look at workflows I may have already found the fix. It looks like if I go to add a "transition" within the work flow, I'm prompted for a "Screen" to add. Should this be all I need? That is indeed the place where you add the screen to appear at…

Hi @Giorgi Nadareishvili, After some playing around, I don't think so. Next gen projects are designed to be as simple as possible and - well - that's how they behave. The closest I could get to what I think you try to do, is work the other way around. So: switch the board into sub-task view and then filter those subtasks…

Hi @Виктория, This is not something available out of the box in Jira, but it can be accomplished using ScriptRunner - more specifically using the Behaviours module. A how to is available in the app documentation

Hi @Stefanie Sullivan, Yes, it is. Adding an extra issue type for program level initiatives is part of the process, but you are right: that alone does not enable the additional hierarchy and roll-up of planning, estimates and progress. The link @Trudy P Claspill shared about Advanced Roadmaps Cloud is the link to detailed…

Hi @Thayne Munson, No. It is not designed like that. You could have a look at some workarounds in this related question 

Notice the difference:

Hi @Ted Stepanoff, yes it is. I know. And you can type in it:

Hi @Ted Stepanoff , Your search is case sensitive. So could ypu check if you can still see the group where you created it (in Admin / Groups). And when you search for it in the groups box of global permissions, make sure to use the same case. Hope this helps. I know I've head a couple of headaches because of it sometimes.

Hi @Gonzalo Benitez de lugo, Have you tried writing the full JQL statement in your issue matches JQL condition instead of referring to filter = 10010? I assume: fixVersion != earliestUnreleasedVersion()