Jack Brickey Expert

this is not currently possible. there are open suggestions for these features. Find one that you like and vote/watch.

I use an addon for this. There are several but I use Automation for Jira. There is a lite version that is free for 300 automations/mo.

@Rachel Hogan , I too would be interested in the response on this. At least in my instance I still have this option.

Parallel sprints are not supported in NG projects as yet.

Ok. And they do or do not appear under People? If they do, what roles are they defined in?

This cannot be changed for cloud.

@Albertus_Boer , I’m not familiar with this feature as I am on Cloud. With that said, this is a forum largely consisting of user like yourself. Your feedback might be best suited for Atlassian Support directly.

Create a search filter using either Basic or Advanced mode and once you have it the way you want save it. Then click details and select “subscription “. Define the interval and recipients. If you want you can create a group under Jira Settings > user management, add members and then reference in you subscription.

Do these individuals have site access and are you simply wanting to remove from the one project? If you have the “anyone” permission selected under customer permissions that might explain it. If so you could change to customers my team adds. If you want to remove the user altogether then you can do that from Jira settings…

I’m looking forward to Summit for sure. While I’m not a huge Vegas fan it can be fun and I’m sure it will be for Summit. If you have never seen the Cirque du Soleil Love and have a chance I highly recommend it even if you aren’t a Beatles fan (do those people exist?). Can’t wait to see everyone!

Thanks for the update Mariah. Indeed it is not enabled by default for JSD and confirmed it is not for mine. @Marc Pflieger I also verified that I see the Sam behavior with blank page except for sidebar. I had to add a test Kanban board to test this as I do t use Kanban for my JSD projects by default.

ok so you are looking at a JSD project not JSW. You will find "issue layout" for JSW projects if you have those. Now where are you clicking on "configure" exactly?

screenshot?

@[deleted] , can you please clarify? I don't understand what you are trying to do here. Are you wanting a report that that shows the number of issues in each priority for every release version or something else?

@Tony Rodgers , welcome to the Community! Yes you can do this. Maybe not in the same way you are used to (a tab) but I think you will find the options acceptable. In JSD you have Agents (those that work issues) and Customers (those that report issues). You are able to view history for either one. That is you can look at…

So i'm guessing the priority is getting adjusted thru automation which likely is running after the ticket is actually created. this would explain why the first notification is showing general. Can you confirm? If this is not how you are setting the priority can you please detail that here?

if you are trying to change the Jira default field "Resolution" where you set the value e.g. Done, Won't do, etc. then you don't want to add another field at all. I assume the issue you are dealing w/ is that you can't edit the field once the issue is in the done status. there are threads out there discussing this and here…

So not a great answer but you can modify the automation as needed. That is if an org is delinquent then when an issue is created from members of the org then deflect the question. When they pay clear the automation. you cloud do this with a single automation and mange multiple delinquent orgs. Remove/add the delinquent…

@Susan Hauth _Jira Queen_ , In fact that should work. The open question in my mind is how to add a property to an org? Ideally you could add a property to an org that would reflect their support status: active, overdue, inactive, etc. but orgs don’t have properties so how to solve?

This isn’t an issue. As long as you are using the SEN only on one instance you will be ok. There is a document that explains migration to new server. Go to support.atlassian.com and search the docs when you need it.

That is good to know! I did not find that in the docs but search was brief and I found the JAC issue. So I actually just checked on my cloud instance and see the same capability. So I’m assuming the issue is that even if you select the option as shown the agents could still create customers but not within an org. Is that…

Here is what I am thinking and suggest you try. * I assume you are saying that if the organization has not paid their bill then all customers in the org will not be serviced * I think you could use the Automation for Jira addon and when a ticket comes in from the domain associated with the payment issues then the ticket…

it is pretty simple. * create backup of current server if you need/want * install a new instance * apply current SEN to new instance * restore from backup but here is the documentation you will want to review - migrating-jira-applications-to-another-server

Hi Hollie, currently you cannot prevent agents from creating customers. there is an open suggestion for this - JSDSERVER-5463 and for any cloud user that stop by here there is a similar request - JSDCLOUD-5640

@Ali Sanne , thank you for sharing this info. The numbers are truly staggering, at least to me. I knew the Community was growing simply thru observation but I would not have guessed these numbers. While I'm sure a large part of this is due to natural growth imparted by the success of Atlassian products I am quite sure that…

I while I have not tried this I doubt that the relationship between epics and tasks will remain. Here is what I would suggest. * create the new project * use bulk move to move all tasks under one epic to new project. * create new epic and bulk edit the issue to add epic link to new epic * repeat as required

While I personally rarely use NG projects there are quite a few folks in my company that use them. Primarily our usage is limited to business projects. I’m seeing more and more folks using them or certainly trying them in the community so adoption is on the upswing. Still I’m partial to classic today.

@Michael Gaskin , i will tell you what I know on this but since I am on cloud and not server the 'approve button in email' isn't supported. however, as you are on server you are in luck as I understand it. Here is a thread that explains how to get that to work - Approve-button-in-email. now as for the approvers please go…

as you noted it isn't an option today. I suggest clicking feedback and letting them know you are interested. I assume you are wanting a "user picker" field.

No date has been committed. I recommend watching the public roadmap page though they don't indicate dates there.