Jack Brickey Expert

@Nancy Tcheou , welcome to the Community. It looks like you are trying to create a classic project. Is that what you are wanting? You can only use the "Share setting w/ an existing project when creating a Classic project and you can only share from another Classic project. When you create a NG project it is completely…

Correct you rarely, in my experience, want a field "required" beyond the Jira default system fields, like summary, etc. What you want to require the field to be completed during a specific transition. I don't understand why this does not meet your requirements based upon what you have conveyed but i'm not 100% aware of…

Hi @E Malik , NG projects are intentionally less flexible in an effort to make them less complex. The downside is, well...flexibility. You cannot restrict access to individual features, e.g. backlog or roadmap at least today. Further there is not support for quick filters as exist w/ Classic boards which would allow you to…

correct it cannot be done OOTB.

@Liz_Pat , i'm trying to follow you here. Any unmapped status simply means that if any issue in the project(s) associated w/ the board are transitioned to any of the unmapped statuses then they will not be shown on the board. Of course the issue are still there they simply are not shown on the board because the board has…

It will send a notification to: Reporter, Request Participants and Watchers. One exception, if you are using Organizations and an organization is shown under the Request Participants it does not send the notification to all customer in the org, just those that opt into being a participant.

Two possiblites: * Check permissions - what user account is running the automation and do they have permission to comment? * what is the IF condition? Is it possibly failing

No engineers use as agents. I have the following users by function: IT (4) HR (2), Facilities (2). We have about 260 employees. On setting up collaborators I think I picked up some tips in the Community. When I set this up I don’t believe there was an article in the getting started guide. It may be ther now if not I would…

@[deleted] , unless it has recently change Epics are not removed when done but again that may have changed as I know they are rolling out updates pretty frequently. Other issues, e.g. Stories, Tasks, etc will be dropped after being done for 14d. So it will be interesting to see if Epics follow suit. 

consider the following... * create a jql to find them all * bulk edit and add a unique 1-time label * edit the board filter or sub-filter to exclude those w/ the label

note i have edited this as my original response was not clear or precisely accurate... to be clear just because an issue is shared w/ the organization a member of the org will not receive notifications for an issue unless they choose to participate. Not if you have enabled the "Organization added" under Customer…

@Andy Griffiths , yep sorry for the confusion I was thinking kanban and not scrum. So assume you are getting a warning that you have un-estimated issues when starting a sprint but you are wanting to block starting, correct? I expect you may be able to achieve w/ an addon; maybe Scriptrunner or Power Scripts but not sure. I…

this seems odd to me TBH. My experience is that if issues are shared w/ the Organization and assuming I add myself as a participant then I should be able to see all Open issue and Open includes 'not yet approved'. i'm perplexed as to why a customer would not see non-approved issues. can you verify that a customer that…

i really cannot say TBH. If you are saying that it used to be one way and now mysteriously changed I would recommend reaching out to Atlassian Support. Particularly if you are on cloud as they can then login and have a look.

Hi @David Rome and welcome to the Community. On the surface things seem ok and therefore should be resulting in the invitation email. A couple of thoughts/questions: * are you seeing the new users being added? * if you make a public comment on their first ticket do they get a notification? * are you sure the email isn't…

@Tariro Rarayi , first let me convey that using the portal will keep things private as long as you configure customers and organizations correctly. As far as being able to reorder the email responses AFAIK this is not possible. 

i haven't played w/ this in awhile TBH as I don't have the need but try this.... if the agent creates w/in the application they should immediately change the reporter/creator from themselves to the customer. they use the Notification Helper to see what the results are.

I can't say how it got setup originally but I see you have 6 members in jira-administrators so I would simply go edit those user and remove them from JSD app.

i would recommend you report this to Atlassian Support

are you trying to notify the approver that an approval is required? If so are you approvers the CEO/CIO respectively? If so you don't need the custom field you simply configure your approvers when setting up the approval workflow. On the other hand if you are simply wanting to notify an interested party when an issue is…

I agree that having Automation pretending to be an actual person is confusing and as such I use a “system user”. I wish that Atlassian provided an automation user for this purpose but alas... so I just use some available system user. You find these in user management.

For sure. * create a new screen that includes the estimation field * edit workflow * Edit the transition from the ‘backlog status’, probably To Do to In Progress, or whatever is your case * add the new screen * add a validation requiring the field * publish the workflow

You don’t want the field to be mandatory that is what is causing the issue. You want the field to be “required” for the specific transition in the workflow. * Make the field optional * define a new screen that has the vendor field on it and any other desired fields for the transition * Edit workflow and edit the transition…

I added JSD to my cloud instance a few years back. JSD and JSW generally work well together but it takes a bit of work to make that happen. You need to leverage Create Linked Issue in conjunction with Automation to make things work well and that takes a bit of trial and error. Setting up JSW collaborators is also not…

you might want to vote for the suggestion listed above in the response from Keri.

you can do one of the following: * construct a jql that excluded the current sprint, e.g. project = myproj and sprint != myproj sprint 15 and sprint non "empty" ....replace the two terms in italics w/ yours. This will yield all issues that have been in a sprint except for the designated sprint. * go to the project in…

got it. So you really want to clone a project not a board. there are some good threads on this in the Community so I would suggest using the search bar. There isn't a clone per se but there are things you can do to reuse aspects of your old project: schemes, workflows, etc. 

there is an addon apps that can do this as I understand but I have not personally used and of them. If you want free then you can consider stepping away from the OOTB queues and use a dashboard and/or kanban board for your agent.

@Romain , this really should be a new question as it seems different. That said.... * first understand that boards are just visual representations of issues in one or more projects they do not define the workflows. * if you have a new project and you are looking to create a board that looks/behaves similar to an existing…

If you want the customer to be associated to the ticket as the Reporter they must be defined as a “Customer” within JSD. You could create a custom text field and have the agen simply type in the sales person’s name. The question is how does the ticket get opened? The sales person would not be allowed to log into the portal…