Jack Brickey Expert

Sprint not in openSprints() and (resolutiondate >= 2020-01-14 AND resolutiondate <= 2020-11-23)

rather than chasing out of process conditions why not take an automated approach to ensure things work the way you want. Use Automation to move the Epic to In Progress as soon as the first story is moved to in progress. If that is of interest just let me know. 

Hi Andy, welcome to the Community. Each project will appear as a ‘card’ on the main help center. Each card is a portal with request types, knowledge based, etc. if you give all your customers access to each project they will be able to creat issues in each project. Now if you truly want or need a single portal, I.e. one…

Yes. 

you should be able to just simply use sprint not in opensprints() and resolutiondate between the dates that you want

I get that it is confusing for sure. the issue is (i think) that if the agent leaves themself as the reporter then they will get the email. I just verified it happens for me whether I create using "Create" or "Raise a request". If the agent uses an email to create they should then update the ticket to specify the customer…

actually the agents really should use this method to open an issue on the customers behalf but when they do they should enter the customers name in the "on behalf of". if they leave their name in there then they are the reporter and would get the email.

try this.... issuetype in (Bug, Story, Feature, "New Feature", Enhancement) and (project in (x1, x2, x3) AND priority != "Not Prioritized") OR (project in (x4) AND status= "Selected for Development")

i have been meaning to try this out as pre-automation the approvers list is so cumbersome. I have uninterested parties getting notified that an issue requires approval. Thanks for reminding me to give this a go @Davin Studer Hopefully @Shannon you will test it out before I get to it. ;-)

User management > JSM = portal only Customer BUT that is only true if you do not have that same email address under User management > Users. This can happen thru various scenarios, namely not using "Migrate user" when you take a Customer only user and give them app access User management > User - if they have any app check…

sure that is possible. for queues, just edit the queue and add createddate to the display. for the issue view just add the field to that screen.

consider using JQL in your condition - request-channel-type = email. You have the following channel types: annonymousportal, api, email, jira, portal. You could use an If/Else condition block.

las columnas equivalen a estados. En los proyectos clásicos, puede asignar varios estados a una columna, pero seguirá apareciendo como una sola columna. Cuando arrastre y suelte una tarjeta en una columna de varios estados, observará líneas de puntos que describen las opciones. Dudo que esto sea lo que quieres, pero solo…

So your first JQL is flawed as you are asking for issues that have two types and an issue can have only one type. A correct filter might be... Project = (project name) AND issuetype = Feature AND Status= Funnel OR (Issuetype = story and status = In Progress) with that said i'm a bit concerned with the potential…

Can this not be solved thru unique Request Types that have the required form (fields)?

my personal preference here is create a sub-task for each reviewer and assign to them. when both sub-tasks closed then the task can automatically be closed. You can also consider using a checklist addon but it doesn't really address the assignee as well as sub-tasks.

what does "move from two different workflows" mean? issues do not move between workflows. you can Move an issue from one issuetype to another where the underlying workflows are different.

you could also use Components if that works w/ the added benefit of leveraging component lead for assignment. you could also use Labels but not a big fan. Regardless use Quick filters to allow groups to see only their issues

and I expect eventually you will be able to configure the shelf-life of Done issues so they clear automatically.

Hi Ajith, My guess is that you need to either create all of those users as Jira user (not likely what you want) OR you need to set a Default Reporter to be an existing user in the mail handler you created. What I have done, instead of say using my own userid is to create a single 'email creation user', e.g.…

so if you wanted to see all open issues assigned to your + 'co-assigned' it would be.... assignee = currentuser() OR "colleague" = currentuser() AND statuscategory != done

Hi @Dominique , welcome to the Community. It appears that Colleague is a custom field. Here is a JQL suggest to get you started.... "colleague" = currentuser()

you need to open a ticket w/ Atlassian Support. If they determine a bug is warranted then will open one and let you know. The Mac App issues in JAC are captured as a Component (Mac App) under JSDCLOUD.

yep but don't get the request in OP about "without JSD"

i see that too. never even took note of that before. however, i can't make it look like a "?". If I zoom in it is just a blue square w/ white dot.

yes a screenshot would be ideal. My initial suggestion would be to check another browser. It seems like something may be timing out and not loading fully.

Hi Mark, I will share what I know and observed. Please note that I am on Cloud so my world is different but hopefully some of it applies. * the suggestions are using key words and my experience is to place these key words in the title as that has provided me with the best results. So breaking up big KB into smaller bits is…

Hi Frank, welcome to the Community. Did you inspect the history tab on the issue? One possibility is that there is an automation that is running on behalf of the user. In that case the rule executes as the user.

agree that SLAs work very well for this but TBH I sort of hate using SLAs as "timers" for automations even though I have suggested such in previous posts. It just seems to be a misuse of SLAs. Sort of a use a hammer when I need a screwdriver thingy. If I could hide these 'timer SLAs' then that would be better. Maybe it is…

if this isn't associated w/ JSM and is Confluence only we need to relocate to the proper collection.