youngmon/atlassian-qna huggingface dataset:
Server Capacity required for Crowd installation on separate server
Asked by Geoff Farnsworth:

Planning to install crowd on a separate server. What would be the required

CPU

RAM

Database capacity for the crowd installation.

Similar to following

<https://confluence.atlassian.com/doc/server-hardware-requirements-guide-30736403.html>


Answers:
author: AnnWorley
body: Ayesha and Geoff, I also could not find the Crowd server hardware requirements. With 50 users, I would expect you to be able to run Crowd on the Confluence minimum required hardware:

CPU: Quad core 2GHz+ CPU  
RAM: 6GB  
Minimum database space: 10GB

Disk space will not grow much as Crowd doesn't store any attachments on the file system like Confluence does. My local installation of Crowd takes less than 300mb disk.

I opened a request for our technical writers to post a page for Crowd like: [Server Hardware Requirements Guide](https://confluence.atlassian.com/doc/server-hardware-requirements-guide-30736403.html).

Here is the request, in case you want to comment or vote on it: [Crowd Server hardware requirements guide is needed](https://jira.atlassian.com/browse/CWD-5005)

comments: author: Sebastian Schmidt
body: [@AnnWorley](/t5/user/viewprofilepage/user-id/502040) Im sad to see that an idea in your on team, which is basic in every other product isnt worked on, even after 5 years.


author: Nic Brough -Adaptavist-
body: Crowd is a lightweight compared with Jira and Confluence, you'll probably struggle to buy a server that can't handle it nowadays.

I know of one running on a raspberry pi with 1 Gb Ram, for a small site with only 20 users. It seems fine to us, although the pi is running only a cut-down OS, Crowd, some basic monitoring and a backup routine.

For a bigger site, Crowd runs fine in the default 512Mb, and the database can also be relatively small - I doubt you'll hit a Gb of disk space even when you've got thousands of users.

comments: author: Ayesha Karunaratne
body: I am looking for an Atlassian recommended Server Capacity for crowd installation for an approximate 50 user site. Thank you.


author: Sebastian Schmidt
body: [@Nic Brough -Adaptavist-](/t5/user/viewprofilepage/user-id/781454) Hey Nic, do you have by any chance, information for a sizing of 1000 users and over that to share?


author: Nic Brough -Adaptavist-
body: Well, actually, that Raspberry Pi I mentioned 5 years ago is now handling 2,500 users, serving as the directory for a near complete server stack of Atlassian services.


author: Sebastian Schmidt
body: [@Nic Brough -Adaptavist-](/t5/user/viewprofilepage/user-id/781454) Can i assume your PI is a new one with 4GB RAM and 4+ cores?


author: Nic Brough -Adaptavist-
body: Originally, it was a Pi3, but that was running hot. It is now a Pi4 with 2Gb RAM. I'd still not recommend a Pi for this, it should be a proper server, but it doesn't need to be hugely powerful.


Tags: install
Does crowdid sever needed always with crowd server
Asked by Hitendra Chauhan:

We have to implement SSO. In order to do this we decided to use Crowd.  

Therefore in the download section, it looks like we have two variety of server application.  

Which one is best for SSO implement ation or CrowdID server is must or only the Crowd Server will serve the purpose.


Answers:
author: Bruno Vincent
body: The download section allows you to download

* Crowd standalone archive
* Crowd Server WAR
* CrowdID Server WAR

Crowd standalone archive includes a Tomcat server, the Crowd Server app, the CrowdID Server app and other demo client applications.

As indicated by its name Crowd Server WAR is just a WAR file that includes the Crowd Server app that is embedded in Crowd Standalone. Its content is basically the *crowd-webapp* folder that you will find in Crowd Standalone. It's the same thing for CrowdID Server WAR whose content is basically the *crowd-openidserver-webapp* folder that you will also find in Crowd Standalone.

You should use the WAR files only if you plan to install the applications on your own application server (I mean not the Tomcat server bundled in the Crowd standalone archive).

If you want to implement SSO on your Atlassian suite, you don't need the CrowdID Server. CrowdID Server is basically an OpenID Server and it's only useful for applications integrating with the OpenID protocol (e.g. Liferay). However, if you're new to Crowd, I suggest that you install Crowd standalone archive. You'll still have the opportunity to remove the CrowdID Server and the demo client applications afterwards.
Crowd over Active Directory
Asked by mcollins02:

I've got a couple questions I was hoping someone could help me with. We've got Crowd connected to Active Directory and was wanting to know the pros and cons of ditching AD all together and using solely crowd.

1. Can we still use it(Crowd) for user management?

2. If we hook it to our domain server, what are the pros and cons?

3. Will we still be able to manipulate permissions on our users if we don't have access to modifying the members of AD groups?

4. Can we have AD users in crowd controlled groups?

<br />

Thanks in advanced.


Answers:
author: Bruno Vincent
body: 1. Yes, you can still use Crowd for user management. In that case, you will store users and groups in an [internal directory](https://confluence.atlassian.com/crowd/configuring-an-internal-directory-18579551.html).

2. Well, Active Directory is often the cornerstone of identity management as every user in the organisation usually has an AD domain account. Linking your Crowd server to AD will allow your users to authenticate on your Atlassian suite using their AD username and password. If your organisation centralises groups management in AD, you will also be able to retrieve all these groups and group memberships and use them in your Atlassian applications. It's a very generic speech but unless you expose your applications to the internet, there aren't many cons about linking your Crowd server to your AD domain.

3. Yes you will as you can select the *Manage Groups Locally* option in the [LDAP/AD directory connector](https://confluence.atlassian.com/crowd/configuring-an-ldap-directory-connector-18579550.html).

4. Yes, that is the purpose of the *Manage Groups Locally* option.
How to limit notifications to be sent from Sandbox to people in a group ?
Asked by swapna baswa:

We have 10 people in a group. Notifications are being sent out to this group through automation upon creation of requests etc. Unfortunately when we test something in sandbox, all of the 10 people are getting notifications. Out of the 10 people, only 5 have access to sandbox. Expectation is when a request is created in sandbox only those five people should get notifications. Unfortunately since all 10 are in the group, all 10 are getting emails. Please suggest how to resolve this issue.


Answers:
author: Jack Brickey
body: Hi [@swapna baswa](/t5/user/viewprofilepage/user-id/5570143) , you should modify the group in the sandbox to remove the unwanted.

comments: author: swapna baswa
body: in my administration page, the groups are common for prod and sandbox. The unwanted are only unwanted to receive notifications from Sandbox, and should be getting notifications from Prod.


Tags: cloud

jira-service-management

jira-service-management-cloud
How to change the status from in-progress to Acknowledged
Asked by Megha Mawa:

I accidentally changed the status of a change from acknowledged to in progress as it is going to be performed after 2 days. I need to reverse the action like i need to change the status from in progress to acknowledge again. Please help me over it?


Answers:
author: Mark Higgins
body: Hi [@Megha Mawa](/t5/user/viewprofilepage/user-id/5570187)

If you can not find the reverse, then that would indicate that the workflow currently does not allow you to move from 'In Progress' back to 'Acknowledge' and you will need to update the workflow, or ask the Jira Admin person to do so, for that to happen.

In the example below, the Awaiting Implementation status can transition to the items listed below it:

![Screenshot 2024-08-17 143517.png](https://community.atlassian.com/t5/image/serverpage/image-id/342312i8F1E44FA30456E5F/image-size/large?v=v2&px=999 "Screenshot 2024-08-17 143517.png")

So you can move to Implementing, Canceled, Completed or Failed.

If you View the Workflow, you will see the arrows that show you the transitions:

![Screenshot 2024-08-17 143453.png](https://community.atlassian.com/t5/image/serverpage/image-id/342313i20974E5E3EB6FED5/image-size/large?v=v2&px=999 "Screenshot 2024-08-17 143453.png")

You can see the arrows and the direction the transitions go.

From what I can gather, your workflow does not allow you to transition back, from In Progress to Acknowledge.

Hope this helps

Mark


author: Seon Shakespeare
body: Hi Megha,

Welcome to the community!

To change the status of a Service Desk ticket, open the change request and look for the "Transition" button or menu (usually near the top-right corner). Select "Acknowledged" if it's an option.

If you don't see "Acknowledged" you might need to transition to a different status first. Click "View Workflow" (if available) to see the possible transitions.

If you're still stuck, your Jira admin should be able to help you figure out the workflow.

Hope this helps!

comments: author: Megha Mawa
body: In the workflow I couldn't find the flow for going reverse that is acknowledged action.


author: Seon Shakespeare
body: Hi [@Megha Mawa](/t5/user/viewprofilepage/user-id/5570187)

It sounds like you'll need to edit your workflow to add a transition from "In Progress" back to "Acknowledged"

* **If you're a Jira administrator**, you can do this yourself. Let me know if you need help with the steps.
* **If you're not an admin**, you'll need to ask your Jira administrator to make this change for you.

Hope this helps!


author: Joseph Chung Yin
body: [@Megha Mawa](/t5/user/viewprofilepage/user-id/5570187) -

Welcome to the community. To supplement what others suggested, you will need to customize your WF associated with the issue type (which supports your specific Request Type) to create a transition back to Acknowledged status from In Progress status.

Once you modified the WF, remember to publish your draft so the new customization will be lived.

Hope this also helps.

Best, Joseph Chung Yin


Tags: cloud

jira-service-management

jira-service-management-cloud
Is there any way to organize customer feedback queues into folders/thematic groups?
Asked by Jason Sadler:

We're beta-testing our platform and receiving a lot of feedback from beta-testers in the Queues section. I am keeping an eye on this portal and assigning the testers' feedback to our product manager. I'm worried that as we scale and start getting more feedback, the influx of issues will become overwhelming. Thus, I'd like to be able to thematically group feedback into something like a folder. For example: putting all of the pieces of feedback about login/logout problems into one folder. Is there a way I can do this?


Answers:
author: Mikael Sandberg
body: Hi [@Jason Sadler](/t5/user/viewprofilepage/user-id/5570113),

Welcome to Atlassian Community!

JSM does not have folders, but what you can do is using Components to categorize the requests, and you can then create different queues for each category.


Tags: cloud

jira-service-management

jira-service-management-cloud
How do I add a customer to JIRA without email?
Asked by Emmerentia Jacobs:

Our clients interact with our JIRA service desk purely via WhatsApp (we use the WhatsApp connector for JIRA). We want to update the generic reporter from WhatsApp connector for JIRA, to be the actual client, but we do not have an email address for our client, only their mobile number. How do we add our clients as customers in this scenario?


Answers:
author: John Funk
body: Hi Emmerentia - Welcome to the Atlassian Community!

You can't add any users in Jira (including customers) without an email address.

However, you can allow anonymous users to create issues in Jira Service Management projects.

<https://confluence.atlassian.com/servicedeskcloud/blog/2017/04/introducing-the-login-free-portal-for-jira-service-desk-cloud>

comments: author: John Funk
body: You are welcome and best of luck!


author: Trudy Claspill
body: Hello [@Emmerentia Jacobs](/t5/user/viewprofilepage/user-id/5570099)

Welcome to the Atlassian community.

I don't think you can add the user as a customer in that case.

To be able to specify a user as a reporter, assignee, watcher, or participant they must have an Atlassian account. All Atlassian accounts are based on an email. Therefore, the customer can only be specified as the Reporter if they have an email and an Atlassian account exists for that email.

If the WhatsApp connector provides the user's name, you could record that in another field. But you can't set it in the Reporter field.


author: Emmerentia Jacobs
body: Thank you for the feedback [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011) and [@John Funk](/t5/user/viewprofilepage/user-id/7148) ! We will look into using custom fields to link all a customer's communications to form a single view of each our customers.


Tags: cloud

jira-service-management

jira-service-management-cloud

whatsapp
create jira ticket with expected request type using API post call
Asked by Wendy Wei:

Hello,

I am able to create a jira issue using custom API post call, however, I cannot map request type field. in our environment, the request type field is inside a custom field as below:

"customfield_10010": { "requestType": { "id": "237", "_links": { "self": "<https://appliedsystems.atlassian.net/rest/servicedeskapi/servicedesk/9/requesttype/237>" }, "name": "Employee Termination Request", }, },

what is correct format on json payload I should use when post via API call? I keep getting 403 error: "body": { "error": "Failed to parse Connect Session Auth Token" }, "message": "403 Forbidden", "description": "HTTP Request Error",

I can create a jira ticket, then using API put to update request type field as second step, but I cannot populate this field while creating issue in one step.

Any idea or suggestion is highly appreciated.

thank you

Wendy


Answers:
author: Fernando Eug?nio da Silva
body: [@Wendy Wei](/t5/user/viewprofilepage/user-id/5509684) ,

If you are using the Jira Service Management API to create this ticket, I recommend using this documentation to map the request type id.

[The Jira Service Management Cloud REST API (atlassian.com)](https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-request/#api-rest-servicedeskapi-request-post)

In this case, the format is: "requestTypeId": "25",

-----

But if you are using the standard API to create an issue in Jira ([The Jira Cloud platform REST API (atlassian.com)](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-post)), you should use the following format for Request Type

"customfield_10010: "request-type-id"

Have you tried one of these?

comments: author: Wendy Wei
body: thank you [@Fernando Eug?nio da Silva](/t5/user/viewprofilepage/user-id/4606715) . i got it working by using the "requestTypeId": "237". :)


author: Fernando Eug?nio da Silva
body: [@Wendy Wei](/t5/user/viewprofilepage/user-id/5509684) , Glad to know that worked!

Please, click on '**Accept Answer**' to help other users with the same question to find this answer more quickly :)


Tags: cloud

jira-service-management

jira-service-management-cloud
Connectivity mail logs "Circuit breaker is open..."
Asked by Jim Ruby:

These appear to be a transient error that doesn't cause a problem but I was wondering if there is a reasonable way to stop them?

"CircuitBreaker 'jepp.outboundauth.token.connection' is OPEN and does not permit further calls"

"Unexpected response received from jepp.outboundauth.token.connection response with status 502"

Thanks.


Answers:
author: Sonya McNeely
body: [@Jim Ruby](/t5/user/viewprofilepage/user-id/5296019) ,

We also had these; they started on August 6th and stopped on August 16th; with no change on our part. I cannot be sure if ours were pausing or stopping the fetching of the emails. Did yours prevent the fetching of emails? Did your errors stop?

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/348453i2DD20720DC0C8758/image-size/large?v=v2&px=999 "image.png")

comments: author: Jim Ruby
body: I had kind of stopped looking at the logs because this wasn't causing any problems (that we were aware of), but I just checked and they stopped on Aug 16 just like yours. And similarly, we didn't make any changes around that time either.


author: Sonya McNeely
body: Yeah, I can't confirm any actual problems for us (besides the logging), and since it ceased the same time yours did I'm chalking it up as an Atlassian blip and moving on. Thanks for the reply.


author: Jim Ruby
body: [@Jack Brickey](/t5/user/viewprofilepage/user-id/853369) We have a team project in JSM that's showing the errors in the e-mail channel connectivity log. They happen at somewhat random times and don't seem to be affecting the incoming messages. It's just some clutter that makes me wonder if there is some underlying issue we need to address.


author: Kevin van t IJssel
body: All of a sudden I experience the same. Since atleast august 12th and nothing has changed on the Microsoft 365 end though. Seems like a bug on Atlassian Cloud side. Because of this, e-mails aren't being imported anymore.

![Schermafbeelding 2024-08-19 093237.png](https://community.atlassian.com/t5/image/serverpage/image-id/342385i0C51B13E65A3BA8C/image-size/large?v=v2&px=999 "Schermafbeelding 2024-08-19 093237.png")   

comments: author: Jack Brickey
body: I would send a request to Atlassian support to have them check it out.


author: Jack Brickey
body: [@Kevin van t IJssel](/t5/user/viewprofilepage/user-id/5571099) , if you do open a request with Atlassian, please update is here with the outcome.


author: Jack Brickey
body: Hi [@Jim Ruby](/t5/user/viewprofilepage/user-id/5296019) , these appear foreign to me in native JSM. I wonder if this is related to some addon app? Where are you seeing these messages?


Tags: cloud

jira-service-management

jira-service-management-cloud
Get image permalink from form upload
Asked by Maximillian Tjhi:

hello my jira friends,

i have 2 attachment fields in one particular form schema. when i export it to XLSX, i am greeted with ![Screenshot 2024-08-16 152208.png](/t5/image/serverpage/image-id/342274iDF9F3BDB2FFCCEE0/image-size/large?v=v2&px=999 "Screenshot 2024-08-16 152208.png")

what can i do with this? i've already tried appending my org's atlassian site name before it, but these values change (even when I've right clicked get image link.)


Answers:
author: Maximillian Tjhi
body: ideally, i'd like a permalink to the image. if i have to use box or something i will do it. any tips are really appreciated!

comments: author: Maximillian Tjhi
body: I've solved my own problem - if anyone wants to know feel free to ask - it's rather long haha


Tags: cloud

jira-service-management

jira-service-management-cloud
Sprint field does not appear even after adding it to the screens
Asked by Ana Luiza Chagas:

Hey guys!

My team and I are trying to solve the following problem: The Sprint field does not appear in Incident type items after closing the item, making it impossible to edit. In service request items, the sprint field normally appears without problems.

1- I have already added the sprint field to my incident creation and editing screens, but even so, after closing the item, the field does not appear and we were unable to fill it in. Has anyone seen something similar?

Thanks for the help!![sprint field.PNG](/t5/image/serverpage/image-id/342236iD21BCD1995C9F87A/image-size/large?v=v2&px=999 "sprint field.PNG")


Answers:
author: Trudy Claspill
body: Hello [@Ana Luiza Chagas](/t5/user/viewprofilepage/user-id/5147899)

Can you provide more information about your scenario?

What screen are you viewing for the closed items? Is that a screen being viewed by the agent? If you pasted it in your message it appears to have not come through.

Are you managing JSM issues in sprints?

Why do you want to edit the sprint after closing the item?

comments: author: Ana Luiza Chagas
body: Hi [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011)

I managed to resolve the issue by editing the item type properties, making them accept changes after they had already been closed.

Anyway, thanks for the reply!


Tags: cloud

jira-service-management

jira-service-management-cloud
Send filled form to a subtask
Asked by Aline Carvalho:

I need to send the filled form of a Created Issue to the subtasks that I will create via automation. Is it possible to do this?


Answers:
author: Adolfo Casari
body: [@Aline Carvalho](/t5/user/viewprofilepage/user-id/3885075)You need to copy the whole form to the subtask or the fields in the form that are mapped to jira?

comments: author: Aline Carvalho
body: Hi,

I need to copy the whole form.


author: Shikha Verma
body: Hi [@Aline Carvalho](/t5/user/viewprofilepage/user-id/3885075) Welcome to the community!  

Yes, it is possible.   

* **Create an Automation Rule**

* **Set the Trigger**

  * Set the trigger to **Issue Created** if you want the automation to run when an issue is created. Alternatively, you can use a different trigger if needed.
* **Add a Condition (Optional)**

* **Create Subtasks**:

  * Add an action to **Create Sub-task**. You can specify the subtask details here.
  * While creating the subtask, you can map fields from the parent issue to the subtask. For example, you can map the summary, description, or custom fields to the subtask fields.
* **Copy Form Data**:

  * If you want to copy specific form data (fields) from the parent issue to the subtask, use the **Copy from Trigger Issue** option when setting up the subtask.
  * Select the fields you want to copy, ensuring that the subtask receives all relevant data from the form.
* **Set Additional Actions or Conditions**:

  * You can add further actions if you need to modify the subtask after it's created, or you can add conditions to ensure the automation only applies under certain circumstances.
* **Publish and Test**


Tags: cloud

jira-service-management

jira-service-management-cloud
SD Bulkfilter - Multiply e-mails
Asked by Peter Huynh:

We have the issue that a lot of e-mails of differnt sender are rejected with the reason multiple e-mail.

Is there a solution except to put the sender on the SD Bulk filter whitelist?

Thank you!

![image.png](/t5/image/serverpage/image-id/342186iF66EFF59A9C27F1C/image-size/large?v=v2&px=999 "image.png")


Answers:
author: Samuel Gatica
body: Hi [@Peter Huynh](/t5/user/viewprofilepage/user-id/5569927)

Welcome to the community!

How are the emails being generated? Occasionally, certain applications may include email headers that classify them as bulk mail. To mitigate this, you can add the domain to the allowlist, which should help prevent it from being categorized as such.

For further assistance, please refer to the following link [Manage your allowlist](https://support.atlassian.com/jira-service-management-cloud/docs/manage-your-allowlist)

Best regards

Sam


Tags: cloud

jira-service-management

jira-service-management-cloud