Jack Brickey Expert

Regarding the Automation route be sure to consider the global/multi-project limitations of Automation if you are on Standard/Free. Whereas the Workflow solution does not come with limits, Automation does. For Automation you can avoid the limits by copying the rule and applying to each individual project rather than global.

Hi @Ben Weisman , Sorry for the delay in getting back to you. I am not always online in the community. Have you made any further progress on this or do you still need assistance? I could try to play with us a bit later today if you need it. Basically my idea would be to automation rules. The first would create all the…

Hi @vandana_sharma , welcome to the community. If you are referring to syncing issues between two different instances then you should consider an add-on to achieve this. One such addon backbone-issue-sync-for-jira looks promising though I have never implemented personally. While you could attempt to achieve something…

pondering... What about this idea... Using either a custom field or maybe labels, you would flag each sub-task chronologically, ST1, ST2, ST3..., at the time they are created. Your automation rule could then assess which sub task just triggers the rule and using that information could then action on the next chronological…

Hi Ben, I don't believe there's any way to determined/define "next". I wonder if you could create the next subtask once the first one is complete rather than creating them all ahead of time? Could be problematic if the assignee is dynamic.

Hi @Chris.Shadbolt , How do you want to use this information? Have you considered using a custom field for sub-organization? I am unsure how these sub-organizations are identified and defined, but expect that is to be manually done. You could name your SOs using the organization, e,g. Iknownotwhatido-System1. it would then…

So are you good to go here? Should we consider this one complete an answered?

Just to be sure, what is shown under project settings > permissions -- Assignable users for the specific project.

How about this... project = ABC and (resolution is empty and (type = epic OR "parent" is not empty)) OR (resolution is not empty and parent is not empty)

Hi Chloe, welcome to the community. So should we infer that the epic's children may not be in the Done state? Also, are you wanting to exclude or include issues that are not linked to Epics? If you want to find issues that are unresolved forgiven project then one of the following should work. project = ABC and resolution…

Thanks Rachel. I finally was able to locate the enable/disable toggle. The issue was that while Atlas was showing in my product switcher it really wasn't fully installed. I had to go through quite a number of clicks that were rather confusing but once the installation was complete I was able to click on Linked goals and…

Hi @Rachel Lin , I must be missing something as I do not see a means of disabling it under the Atlas cog. Maybe a Free plan limitation?

Correct. Only at system level.

Hi @Marcelo Baratella , if you do not see the System option under the cog then you do not have the necessary permissions. Please seek out your system admin to discuss your desired comment ordering.

Hi @AAlbero , I have not played with Atlas for a long time. Could you share exactly what you mean by "...is now showing in our epics"?

Thanks Paul. So the thing is that none of the numbers really add up based on what you have provided. It seems that maybe some of the disabled users are being counted. I wonder if the difference can be attributed to whether they are an author of any pages. Regardless, unfortunately, I don't have a good answer for you and I…

Can you provide an example image?

Understand but your rule depicted in the image does not reflect your text in the post...so confusing. That said, the rule @Marco Brundel provided should achieve what you have conveyed.

Hi @Joanna Whitley , can you tell us what fields are being set during the creat actions? The error message seems to imply you are attempting to set the value for a field that doesn't exist in the create screen for subtask Issuetype.

Those are transitions not statuses. Regardless, you cannot change how that is displayed in Server. Not that it helps you, but n Cloud the available statuses are shown in a drop down...

If the user is a Customer of a JSM issue then they do not have access to the backend app. They will be directed to the portal. This cannot be changed. Maybe I am misunderstanding your situation though? 

Hi @Inna Kohler , have you looked at creating a dashboard and adding the created versus resolved gadget?

That didn't help me. In the image, are you talking about the grey buttons when you talk about columns? Those are your available transitions based on the current status. I'm struggling to understand presenting statuses in list view.

I did find this post. Might be worth a go... How-can-I-make-inactive-users-searchable-in-Confluence 

Hi @Paul Martin , have you confirmed your theory of inactive users? This should not be the case. Can you query the number of active users and assess? OOTB, I am not aware of querying pages by user status.

Hi @gina , sorry you are experiencing issues. Can you please provide more info so that I might assist?

Hi @Aasha , can you explain further? What gadget are you using? Where do you wis Status to appear?

You are using a Team Managed Project. Moreover, this is not a Jira Work Management project which is the collection associated with this post. You might find the following article useful in understanding workflows in TMP - set-up-a-workflow-in-a-team-managed-software-project . basically you should do the following... *…

I am unsure how to guide you without understanding more about your situation. I will try to flag this post for further assistance.

I see. I guess the first potential solution for this that comes to my mind would be to create three custom fields: Iteration (values of One and Two), Iteration One Bugs, Iteration Two Bugs. These last two fields would be a number, Field,, representing a count of the number of bugs linked to the issue during the specific…