Jack Brickey Expert

Trial version are fully operational. What do you mean by “activate”. What are you attempting to accomplish? Workflows are ‘active’ if they are associated to an issuetype in a project.

What is your goal of the automation? What Automation are you using, built-in or something like Automation for Jira? If A4J you can run an automation on a schedule (daily) to assess issues approaching due date and trigger another automation.

Ok, so is the reassignment done to the previous assignee and if so will this always be the case? If so I recommend creating a custom user picker field called say “developer”. When resolving the issue copy the current assignee to the “developer” field using a post function. Then add a post function to the reopen transition…

It will be hard to diagnose the issue from here TBH. What version of IE? Note that IE11 support is being stopped in March-2020. Is this a recent issue? We’re there updates made to IE? Do you have any browser extensions?

Yana, I am assuming the client has full access and permissions to transition and assign issues. If not please elaborate on the situation further. What I recommend is that you add a transition screen called say “reassign” and include the assignee field. Edit the workflow and add that screen to the reopen transition. Add a…

You want to “edit” rather than view workflow. In any event the limitation here is that it is a static single user. If the issue is to always be assigned to the same person this will work.

If you have an organization that is shared on multiple projects then the customers are shared as well. So adding a customer to an org in one project will add that customer to the other project(s).

Having portal access is half the battle you need to ensure that the customer is added as a customer in the desired project(s). Migrating a portal only JSD user to a Jira user results in them having application access which is a paid license.

This is what I see. You might want to check with your admins if you are not in fact the system admin. Otherwise reach out to Atlassian Support.

they now offer a Free version of Jira cloud w/ some limitations (permissions, no anonymous access and a storage cap of 2GB). Might be worth standing up as a sandbox.

the question is how are your customer permissions set. If it is "Customer my team adds to the project" then the only way they can be added is by an agent/admin. If "Anyone can send a request..." then they would pop up when an email is sent.

Hi Kevin, i too am glad to see this feature. I just ran a quick test and "seemed" to work for me. this query - type = task and issueLinkType not in ("relates to") - returned 142 items this query - type = task and issueLinkType in ("relates to") - returned 538 now I have not scrutinized the results and TBH would have…

and then after you have access - just don't do it! just close them off. deleting will lead to regret. :-)

how about this... status was "In Progress" AFTER "2019/11/01" if you want to bound it to exclude items that were not moved out of IP by the end of the month.... status was "In Progress" AFTER "2019/11/01" and status was not "in progress" after "2019/11/30"

Community just keeps getting better and better.

I’m not specifically familiar with “trusted” and “basic”. Maybe these are roles or groups that you or another admin have created? Does your Permission scheme show/use these terms? If they happen to be a group or role then you will want to either remove the role/group from the desired permission OR remove the users from the…

Those concepts don’t exist. You might look at Portfolio product from Atlassian. You could create labels or custom fields but may not achieve your requirements. 

Go to id.atlassian.com

Have a look here. jira-sizing-guide 

I’m unsure what your question is or if you have one. 

Please verify that the Resolution field is set for the Done issues.

No. The ticket will be created in JSD. The automation could then mirror this issue in JSW if desired.

I meant the “+”. I was just testing and it worked. Here is what I did. * request types all hidden * i create an issue in the project choosing the Issuetype of interest and one that has request types associated to it. * once issue is created I go into the issue detail view and change the “none” request type to one…

Hi TC, most if not all of your concerns can be alleviated. I thing you are experiencing new user issues. I will try to offer a bit of help but encourage you to look at the documentation at Support.atlassian.com As it will provide a wealth of more details. * seeing many or all issues - you can create filter in Jira and save…

Well, not to proud to admit I was flat out wrong here. Indeed you can do it by projects. I don’t ever recall seeing it before but just check and indeed it is an option for swimlanes. So now the question is, are you not seeing the option? Board settings > swimlanes

My experience with NG shows that the sorting is done manually within the column. So there is not configuration as there is with classic, I.e. ranking. When you drag and drop an issue the order is based on where you drop not where it was in the original column.

Regarding JSW email handler theory, I think it is unlikely but possible cause. Check for this as I outlined above. Look for an email handler associated with your JSD project.

You will need to use the by “queries” and specify the project! E.g. project = a, project = b... obviously this will not be dynamic so you will need to maintain it as project change but those not specified will appear under “everything else” swimlane in the meantime.

for sure you can setup JSD project w/o any SLA - easy enough. you could also do what many folks do where JSD project faces the customer and a JSW project is 'linked' to the JSD project via automation.

I ran into this years ago. Jira doesn't support independent workflows for multiple version w/in the same issue. The only way (?) to do this is to clone the issue for each affects version and treat them independently. Maybe there is an addon that would help here but I am unsure.