Jack Brickey Expert

@Hardik Bhatt , you should be able to see the default Approvers. For me they are displayed before and after I click on the edit default value. If it is blank I have to imagine you do not have Approvers yet defined or maybe the wrong custom field. Jira settings > Issues > Custom fields > ‘approvers’ click On ellipses and…

@Harneet Singh , correct that is what this thread is saying. There is an article that explains how to change from NG to Classic but I don’t have it at my fingertips. You can search the community and find other threads that will point you to it. Basically it is a ‘simple’ matter of creating a Classic project and bulk moving…

...one possible cause is an addon conflict. if you have any you could consider disabling likely candidates and retest.

Agree w/ Alexey but will add that if you are using the default board that comes when you create a project you can optionally create an 'full featured' kanban board. The only caveat is that if it is a non-SW project you will need to create it using your profile as the "Location". Then you can add an URL link in the sidebar…

sure... * create a filter search, e.g. "project = myproject" * once you have your filter producing the exact issues you want to add the label to.. * use Bulk edit, edit issue * add label and submit

depending on the details of the "formulary" this could be done via the built in automation. Can you speak to the details of what fields or means the customer would complete, etc. Otherwise I would simply jump into the Automation under project settings and see if you can create a Custom rule that would meet your needs.

well i'm surely interested in knowing the root cause.

this is what the syntax looks like... assignee = jack.brickey

Hi @Cindy Ticha , I see you also posted here and based on that post I'm assuming it is directly related. Further, what you are looking for is the ability to add some granularity to your backlog. The best thing I can suggest for an OOTB solution is to use quick filters to show what you are interested in and hide the rest.…

what you should do is to edit the workflow and on every transition to DONE (or whatever you final status is) you should add a validation action of requiring the Resolution be set. You also need to add the Resolution field to the screen for those transitions. If you don't have a 'resolution required' screen defined you can…

how would you imagine being able to select a story? I'm trying to imagine a solution but don't really understand the use case or concept of this.

one other test for the curious... can you go to the advanced and change "assignee in..." to "assignee = xxx"? i expect the same error but one never knows.

great. please update here if you get to the bottom of this or not. I'm very curious.

UPDATED>>> To save others time in the future from having to read the gory details below I will offer the following conclusion - JSD agents will not be able to access any Boards unless they have a JSW license. Boards are a component of JSW. However, they can access Dashboards. Read on for the full discussion.... @Thomas…

you don't "assign" but you "share" with a group. if you are the owner of the dashboard just edit permissions and share w/ group. If by "assign" you mean allow users w/in a group to assume ownership permissions then no.

we need the ability to link answers! :-)

it depends. * On cloud or server - you certainly need to have project creation permissions - talk to your admin. The one exception is #2 below... * On cloud - if your admin has enable Next-gen projects then anyone can create a NG project. * On cloud or server - being a project admin is singular to a project it does not…

well if you are absolutely sure the assignee is the same in both "blue" cases then something is certainly amiss. I have never seen this fail. What I have seen is where there are multiple users w/ the same or nearly so name so while you think you have it right in fact it is referencing a different person that is not…

@Esther Strom , correct for those customers they will show up under Portal Only Customers. However, be careful there to ensure you don't deactivate SDA customers. In case that isn't obvious.

when you transition an issue to the "Done" (or similar final state) and set the Resolution value.

@[deleted] , they are working fine for me. I would reach out to Atlassian Support this seems to either be instance specific or you recently were upgraded and something went bad wrong. 

you could configure swimlanes by stories and collapse all but the one of interest

does this work by chance? I have not tried. project = project1 and customfield = A and customfield = B and customfield = C

would the default Components work for you? It has the advantage of setting a component lead among other benefits.

would you mind clicking on the "Advanced" link. it will show you the details of your JQL which will likely lead to the reason. Feel free to screenshot here if it isn't immediately obvious. Aside from that If you select the assignee in the dropdown in the Basic search where the assignee = one of the two issues in the first…

have a look at this article - how-to-migrate-projects-from-one-jira-cloud-application-to-another

i guess that is a custom field on your side. nice coincidence. :-) I'm not sure how Jira keeps/determines this info TBH. You might search the Community to see if you get any clues or maybe the documentation.

I would suggest an addon. I use Automation Lite for Jira (or the non-free version Automation for Jira). Other very popular ones are Scriptrunner and Power Scripts.

Hi Kris, I don't think I will be able to assist w/ this further as it is beyond my experience and don't have access to your system. I would suggest contacting Atlassian Support

the create transition is absolutely in the workflow. it is the first transition from the circle entry point. If there are no validations then I would recheck the field being required. BTW, rarely should you make a field required at the field level. rather you should use the workflow and validation.