Jack Brickey Expert

I misread your request and concur w/ @Brant Schroeder that an addon would be needed (?). You might be able to come up w/ a solution depending on the details still. Such as, you might be able to trigger on "comment added" and condition of "comment contains". But TBH, this could get messy even if it is possible. I expect you…

You should be able to do this using the existing Automation. However, the details of what you are trying to do might take you beyond the built in automation. I use this to update the status of my JSD issues that have development JSW issues linked.

Glad you got it! That is what my #1 above was intended to convey. :-(

so your mention "should" but not 'must' which to me equates to "ideally" but not 'required'. If you want "must" then create separate projects for the two teams. If "should" is ok then my previous suggestions would do the trick.

question - are you also wanting to prevent SupA from seeing teamB's tasks and SubB from seeing teamA's tasks? If not then here is what i suggest: * design your queues to align w/ team A and team B (e.g. by assignee) and give them unique names. This allows the Supervisor to identify them * create a dashboard and lay it out…

Yep. when you reopen an issue be sure to include a post-function to clear the Resolution field.

Email security falls outside of Jira. For example we use Exchange so all security associated with that email must be handled within Exchange. Your IT group would need to address this. However, what the Jira admin then must do is to manage permissions on the access of the issues to ensure only those approved can access the…

On Cloud if you are an admin you can do the first two. On the portal click Customize button. Do you not see this on Server?

This isn’t currently available in NG. You might consider providing feedback via the feedback link.

Sure. Create a dashboard for your project and add a pie chart or similar and use “customer request type”.

You are welcome! Please consider accepting the answer so that it helps other surgeries in the future .

And if they are in the portal, upon page refresh they have a badge icon on their avatar that increments with every new issue.

IMO I wouldn’t place that as the first thing to address among all the current limitations with NG. We have a ton of functionality with Classic projects today and I understand and am a fan of taking an MVP/agile approach to delivering new architectures. NG will continue to get better and Atlassian seems genuinely interested…

@Mary McDonagh, you are welcome. Please consider accepting the answer as it helps others with future searches.

Yes

You need to ensure that the Kanban board is shared. Go to the board and in the top right click on the ellipses and board settings. On the general page you should see a edit filter shares.

@Matt Strautmann, you can always create a classic project and bulk move the issues.

i don't believe versions is supported as yet. here is the public roadmap but not immediately popping out at me.

Note I do not work for Atlassian. With that said all indications, including a recent Webinar presentation and associated AMA, are that there are no immediate plans for this. Consideration will be based upon the success in Cloud and working with the Server PMs.

is the automation being executed under your user id? if not be sure that the userid being used has permissions. The labels vs. your condition doesn't matter. if you want you can remove the condition altogether and test but expect that is not it. 

I just tested and it works for me. Below screenshots might help...

That is correct. you may be interested in this issue? JSDCLOUD-5746

but you can always provide feedback to Atlassian via the feedback link.

I may not be following you precisely but you can certainly create a query based upon labels. It is unclear to me how you will use labels for this exactly and that understanding might influence my answer. That said... if you don’t have too many labels you could create a dashboard with a pie chart by labels and it would…

LOL! Didn’t recall that being there, that’s what happens when you never log off. 

By default there isn’t and agent name in the email so this must have been added in your instance. Go to project > project settings > customer notifications and edit the appropriate notifications to remove the variable that would include the agent’s name. Now if you want a “generic” name you could place actual text vs. a…

If they logout then they have to login but they don’t have to logout. I never logout and most of my users do the same.

@Janet Austreng, welcome to the Community. You can do quite a lot w/ JQL. I will need more details to answer whether your goals are achievable. Can you provide an example?

you should not move between projects as it breaks the connection to the customer's request. What you can do is to open a ticket in Project B and link to Project A and you can use Automation to have the one in Project A 'follow' the one in Project B from a status perspective, i.e. have the one in Project A close when the…

admins do not have to consume an agent license but as an admin you might find you need to. Here is a thread that does a good job of explaining I think.