Jack Brickey Expert

Maybe I don't understand the use case here but if you are using Components you can set the component lead thereby ensuring that any issues will get set to the proper person based upon the component selected.

two separate queues or two separate projects??

how are you selecting things for development in the Kanban backlog? Are you not moving from To Do to "Selected for Development" or something similar? if not I recommend you set the workflow to represent something similar. In my example below "Backlog" status is mapped to the Backlog (column 0 let's say). Selected for…

can you remove all other criteria and simply search for epic link" in (xxxxx)

correct

this sounds odd to be sure. I have never seen this occur unless someone changed or some automation changed it. Is this repeatable? I would certainly run another test and immediately check it. Also, to be clear You are looking at the "Request Type" and not the "Issue Type" here correct? What Issue Type is associated with…

I do not know what you mean by "sub account" If these are two different instances of jira which it sounds like is the case then you will need to do the following: * create new projects in the desired instance to receive the issues form the other instance. This will be a manual effort by referencing the existing projects in…

that cannot be modified at least thru configuration.

Yes you can do that the SEN just needs to be active on a single instance.

I'm thinking you would use an automation addon, e.g. Automation for Jira. The way I would implement would be if a certain issuetype was created meeting whatever criteria then it would trigger the automation to create associated issues for the respective groups. I do this today for onboarding new hires.

i think you are asking how to hide the "Emailed Request" request type? if so go to project settings > request types and edit the groups that Emailed Request has and remove from all groups (check boxes). If you have something else in mind please let me know.

and you have confirmed that you are in one or more of those user roles I assume. If so and you do not see Next-Gen when creating a project then I would contact Atlassian Support.

can you go to Jira settings > system > global permissions scroll to the bottom and see what you have for NG projects

thanks for sharing indeed it is there for me too. Search seems to be reasonably effect though it isn't returning all hits for sure so unsure how useful it will be TBH.

here is a filter that might get you what you want... project = myproject and duedate <= endOfMonth() and duedate >= startOfMonth() and resolutiondate is EMPTY you would set this up as a subscription that runs at the end of the month. it would yield all issues that were due in the past month but not resolved. you can refine…

ah... so you are using the NG JSD project type. :-) while i have created one for the sake of trying it out I have not actually had time to look at it so unsure how you can hide a request type in that project type. p.s. please keep your replies in the appropriate answer thread so it keeps the thread readable. Use "reply"…

Well, there used to be a "Home" screen that was accessible under the "Switch to" icon on the bottom left sidebar but it appears it is gone now. at least I cannot find it. there may be another way but haven't stumbled upon it.

good question I have never observed this. Regardless there is nothing you can do as a Jira admin. you need to be a system admin i suspect so reach out to Atlassian Support.

Olá @Malu , Você pode adicionar campos personalizados à solicitação de criação acessando as configurações do projeto> tipos de solicitação, localize o tipo de solicitação de seu interesse e clique em Editar campos. Clique no campo Adicionar. Se o campo não estiver lá, você precisará primeiro adicioná-lo à tela de criação…

you would need to have Ready for Development in the Backlog column in the board settings > columns

i found the following that might be helpful. it is a rather old work around though. Check the comments in this issue - JRASERVER-21184. not that the suggestion itself was declined.

i think you are asking to display the issuetype and the request type (aka Customer request type). what gadget are you using that you are trying to do this for?

* create the custom field if not already done * create a screen that can be use to request input for the new field * edit the workflow in diagram mode * double-click the transition(s) going into the resolved status * add the screen you created * add a Validate action that requires the field to be filled in and add an error…

on the sprint board go to board settings > estimation and check the "estimation statistic" in use. It should be set to Story points. the issue does not need to be a Story issuetype to use Story Points for estimation. Typically one uses Story Points for estimation and time for logging work.

Can you explain more about where you added sites? What configuration are you speaking about.

he or she will need to be added as a new user in the new instance. they can have the same user id and email as they do in the other but they will have to access the two independently as they are independent instances.

have you inspected the Column configuration under Board settings? Doing so should explain how the board works. In fact you question seems to convey exactly how your board works. The way the board works is that you map one status, e.g. To Do to the Backlog. When issues are created in the To Do status they will then appear…

@Sadia Aslam , thank your for the video. What I am seeing is that you have Jira Labs on which is clear because when you click on the done issue at the end of the video then the resolution is showing beside the status. You have configured to use Dialog view instead of the sidebar detailed view. So all that is consistent…

Seba, unless i'm misreading his question I think Ben is want to simply use a custom email for incoming issue creation not for the notifications back to the customer.

Yes. Just go to project settings > email requests and add a custom email address and use your current helpdesk email.