youngmon/atlassian-qna huggingface dataset:
Populating OpenLDAP from Crowd
Asked by Eugene Tan:

Hello all,

I was wondering If I could get some advice/help. I tried to search "crowd" and "ldap" but nothing came up in the community knowledgebase

I use Crowd as a base for Authentication. Which is great for apps and services that support Crowd directly.

But I have other services and application that only uses LDAP.

Alot of my searches have Crowd populated FROM LDAP.  

However in my case like the title says, I want to use Crowd as the primary source of User and Groups and populate an OpenLDAP server for my services and applications that require LDAP based auth.

I do not have the technical skillset unfortunately to write a custom Crowd connector for each of my apps. So my thinking is to go the above-mentioned route.  

Cheers,

/et


Answers:
author: Bruno Vincent
body: Hi [@Eugene Tan](/t5/user/viewprofilepage/user-id/1198238)

This question has previously been answered on [this link](https://community.atlassian.com/t5/Questions/Migrate-from-CROWD-to-openLDAP/qaq-p/127747).

In short, here is what you will need to do:

1. Export your users and groups from Crowd to CSV files (please follow [Atlassian's documentation](https://confluence.atlassian.com/crowdkb/how-do-i-generate-a-csv-export-of-users-and-memberships-from-a-specific-directory-in-crowd-442271568.html) for this)
2. Create an LDAP Directory Connector in Crowd that points to your OpenLDAP server (again, please follow [Atlassian's documentation](https://confluence.atlassian.com/crowd/configuring-an-ldap-directory-connector-18579550.html))
3. Import the CSV files that you created in step 1 into the OpenLDAP Directory using [Crowd's CSV import tool](https://confluence.atlassian.com/crowd/importing-users-from-csv-files-64454760.html).

The problem is that depending on the password hash/encryption algorithm used by your current Crowd internal directory you might not be able to import your current users' passwords. For instance, "atlassian-security" is not supported in OpenLDAP. In that case you will need to reset your users' passwords.


Tags: crowd-administration

ldap
Adding a new Site Admin
Asked by Brian Romanko:

I am attempting to add someone as a site admin. However, I cannot add anyone to that group. It complains that "You can't add members to this group because this site is linked to an organization."

How can I add a site admin?


Answers:
author: Brant Schroeder
body: If you are an organization admin you can edit the account, I am assuming that you are just a site admin.

You can learn more about organizations here: <https://confluence.atlassian.com/cloud/set-up-an-atlassian-organization-938859734.html> \& <https://confluence.atlassian.com/cloud/get-more-security-and-control-across-your-organization-964957873.html>

comments: author: Brian Romanko
body: Thanks for the suggestion!

I didn't realize there was a separate place to manage Organization Admins. That wasn't clear from the UI. Once I found that page I was able to add the other user.


Tags: cloud
Crowd starts with error
Asked by tw:

Hello \*,

I have copied a user in ubuntu 18.04 incl. installation of JIRA, Confluence and Crowd. Crowd has been set up completely for user management of JIRA + Cofluence incl. SSO for old user. Now after copying all old user files, JIRA + Confluence directories have been all corrected. Crowd as well.

But starting all server there still is an error left at Crowd with a message like: Couldn't save crowd.cfg.xml to /home/\<old_user\>/atlassian/crowd-home/shared directory.

The question now: where to look for this file entry to correct the old user by new one? Might it be saved in the database?

Thanks in advance for help.


Answers:
author: tw
body: Issue resolved.

Besides several files it finally was about the crowd-init.properties file to correct the path / old user.


Tags: crowd-development
Waiting for Approval Status Change
Asked by Sinan Y?ksek:

Hi,

How can we setup the function in Jira in order to lock the status change of a ticket ?

We allowed to send the tickets to multiple approvers and what we want to do is preventing changing the status (on hold, in progress etc.) until all the people approve the ticket. Let's say we will send the ticket for 2 person, if only one person approves, the status change should be locked. If both of them approves then we can change the status.

Thanks in advance.


Answers:
author: Parsa Shiva
body: Hi [@Sinan Y?ksek](/t5/user/viewprofilepage/user-id/5573235) ,  
If you're open to non-native solutions, there's a tool called *[Approval Path](https://marketplace.atlassian.com/apps/1220490/approval-path-for-jira?tab=support&hosting=cloud)* that could work well for your scenario.  
It's easy to set up and doesn't involve much hassle.

To start, you'd need to create an approval definition.  
Based on your use case, the approval won't be finalized until all parties have cast their votes, and if anyone rejects it, the whole process is denied.

Once you've set up the steps in that definition (the steps define who the voters are), save it.  
Then head over to Jira's workflow settings and follow this guide to add a workflow condition: [Approval Path Documentation](https://docs.warsawdynamics.com/content/51604/approval_path_for_jira_documentation/16646179/120029185).

After integration, the status transition will be locked until the approval is finalized.  
You can even configure a post-function in the workflow to start the approval automatically when a specific status is reached.

Best,  
Parsa Shiva


author: Mikael Sandberg
body: Hi [@Sinan Y?ksek](/t5/user/viewprofilepage/user-id/5573235),

Welcome to Atlassian Community!

Have a look at this [KB](https://support.atlassian.com/jira-service-management-cloud/docs/set-up-a-pre-set-list-of-approvers/) on how to set up approvers. Basically you have to go into the workflow that the issue/request is using and on the status that is the approval status enable the approval step. In it you can define if everyone in the field has to approve and what will happen when a user approves or denies.


author: Manoj Gangwar
body: Hi [@Sinan Y?ksek](/t5/user/viewprofilepage/user-id/5573235) ,

Welcome to the Atlassian Community!

You can configure the workflow approval for 2 people so If both are approved then it will be transitioned to the next status.

For more info, please refer- <https://confluence.atlassian.com/adminjiraserver/configuring-jira-service-management-approvals-938847527.html>

comments: author: Manoj Gangwar
body: [@Sinan Y?ksek](/t5/user/viewprofilepage/user-id/5573235) If our responses were helpful please consider clicking on the Accept Answer buttons to mark your Question as Solved.


Tags: approver

cloud

jira-service-management

jira-service-management-cloud

lock
How can I add the purchase price of an object in Jira Assets?
Asked by Markus Windisch:

A crucial aspect of my asset management involves calculating costs for goods that I sell to customers. I need to include the purchase price of the goods to the objects, but there doesn't seem to be a way to do this (especially in European format). Additionally, I'm unable to export the lists to, for example, total up the sold goods.

Is there a way to accomplish this with Jira Assets?

Thanks for your assistance!


Answers:
author: Kevin Patterson
body: Hi [@Markus Windisch](/t5/user/viewprofilepage/user-id/5583155) ,

capturing the costs for ordered goods and calculating totals for an order should not be a problem. For your object attribute I would recommend using Float for your Purchase price and total order price field type. This field allows decimals unlike the integer field type. Automation for Jira can do calculations off of these values and update other asset objects and attributes if required.

Assets does have an export feature under bulk options that will allow you to export an object type and all the objects.

It might be helpful to understand how you are planning on using assets as part of your workflow. I suspect exporting lists is not really what you want, but instead you might be looking for a way to display a customer order with all assets associated to the order as line items.

comments: author: Markus Windisch
body: Hi [@Kevin Patterson](/t5/user/viewprofilepage/user-id/5497084) , thanks for your response, it sounds promising.

I plan to use assets mainly as an inventory system for software services (subscriptions), employee hardware, office equipment, and the goods we sell to customers. The purchase price helps me track the total value of my inventory. It would be fantastic to have an automated calculation of this, visible somewhere within the assets. My accounting team also requires a report on what we've sold to customers, so the Excel export feature is really useful.

I'm not sure how to implement the automated calculation yet. It would also be great if I could filter by categories like PCs, laptops, phones, etc.


Tags: cloud

jira-service-management

jira-service-management-cloud
CCing users
Asked by Ivett Laszlo:

Hey,

I'm trying to add to a form - a "CC user" field where users can add other users to the ticket they are raising. I've only been able to do this in the following way (see screenshot) The problem is the users can't add email addresses here it seems. Is there a way to allow them to add either emails and / or usernames? They've been given permission to invite people to the ticket.  

![jira.png](https://community.atlassian.com/t5/image/serverpage/image-id/345259i2AE636C470B8B8EF/image-dimensions/519x200?v=v2 "jira.png")

On the ticket itself they are able to add more people CC'd in, and I'd like this exact field to be on my form:  

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

Is there a way to do this?

Thanks in advance for the help!

<br />

Ivett


Answers:
author: Christopher Yen
body: Hi [@Ivett Laszlo](/t5/user/viewprofilepage/user-id/5569143) ,

Are the users the customers are adding to the CC already customers in your Atlassian environment? There should be a request participants field that works similarly to CC'ing while in JSM

> Request participants are people who agents or customers have shared a request with. They can view, comment on, and receive notifications about the request. By default, they receive the same notifications as the reporter of the request but can turn off these notifications at any time.
>
> You may add request participants so they can provide more information about a request, or to notify them about a request's progress.
>
> You can add request participants by sharing the request from its issue view.
>
> Request participants follow issue-level security schemes. For example, if an administrator customizes requests so that only reporters can view them, then request participants won't be able to view the request

<https://support.atlassian.com/jira-service-management-cloud/docs/what-are-request-participants/>

comments: author: Ivett Laszlo
body: Some would be some not, that's why I'd prefer having an email as well as user option.


Tags: cloud

jira-service-management

jira-service-management-cloud
Reply on email notification
Asked by Evert Morren Atlas Admin:

When a user creates an issue, he receives an notification. The user can send a reply on the notification, the reply is added as a comment to the issue. But if the user send a second reply on the notification it is not added to the issue. How can I solve this problem?


Answers:
author: Samuel Gatica
body: Hi [@Evert Morren Atlas Admin](/t5/user/viewprofilepage/user-id/4775056)

I was unable to replicate the issue. I created a ticket and sent three replies using the notification email, all of which were successfully added to the ticket.

Can you please confirm the following:

- Are you responding to the same email as indicated in the notification?  
- Does the subject line include the Ticket ID (e.g., XYZ-123)?

Best regards

Sam

comments: author: Evert Morren Atlas Admin
body: Hi Sam,

I have tested it again, sometimes it works, sometimes not. It seems something in our environment. First I will do some further investigation.

Thanks for your reply.


author: Evert Morren Atlas Admin
body: Hi Sam,

It seems to be an issue in our environment, after some changes now ok.

Reagrds,


Tags: cloud

jira-service-management

jira-service-management-cloud
Jira Service Management - Right Hand Side
Asked by Karim Mohamed:

Hi,  

On any given Jira Service Management ticket, if the request type is empty, is there a way to customize the right-hand side and the fields on there ?   

When there's a request type, you can configure the fields but when it's empty, I'm not sure how to do so  

Thank you


Answers:
author: Christopher Yen
body: Hi [@Karim Mohamed](/t5/user/viewprofilepage/user-id/5046408)

Unfortunately, issues without a request type do not seem to have an editable layout at this time.

Here is a suggestion record for Atlassian that you can subscribe to and vote on to let them know this feature would be useful for you:  
<https://jira.atlassian.com/browse/JSDCLOUD-9230>


Tags: cloud

jira-service-management

jira-service-management-cloud
Automation for creating a URL link from a custom field
Asked by Mika Barnett-Ohori:

I want to create a custom URL from a field someone enters from a custom field. If the custom field (labeled Rule ID) is entered as 1000. I want the automation to populate a certain website (format would be something like: <https://website.com/1000/fakewebsite>) where the 1000 could be any number. How do I go about creating this automation in Jira?

Custom field entered (Rule ID) = 1000

then it auto populates a website = <https://website.com/1000/fakewebsite>


Answers:
author: Ashok Shembde
body: To create an automation rule in Jira that generates a custom URL based on the value of a custom field (e.g., "Rule ID"), follow these steps:

Steps to Create the Automation Rule:  
Ensure You Have the Custom Field

Make sure the custom field (e.g., "Rule ID") is already created and available in the issue types where you want to use this automation.  
Go to Automation Rules

Navigate to your project in Jira.  
Go to Project Settings \> Automation \> Create Rule.  
Set the Trigger

Choose a trigger that suits your needs, such as Field Value Changed or Issue Created, depending on when you want the URL to be generated.  
Add a "Create Variable" Action

Use the Create Variable action to store the custom field value. Name the variable something like ruleId.  
Set the variable to the value of the custom field:  

Smart value: {{issue.customfield_1000}}  
Replace customfield_1000 with the ID of your "Rule ID" custom field.  
Add an "Edit Issue" Action

Use the Edit Issue action to populate another custom field where the generated URL will be stored.  
Set the field's value using the following smart value:

<br />

<https://website.com/{{ruleId}}/fakewebsite>  
This will replace {{ruleId}} with the actual value entered in the "Rule ID" field (e.g., 1000).  
Save and Activate the Rule

Save the automation rule and activate it.  
Example:  
If the "Rule ID" field is set to 1000, the rule will automatically generate the URL <https://website.com/1000/fakewebsite> and populate the specified custom field with this URL.

Testing:  
Create or update an issue where the "Rule ID" field is populated.  
Verify that the URL is correctly generated and stored in the custom field as specified.

comments: author: Mika Barnett-Ohori
body: thank you!


author: Jovin
body: Hi [@Mika Barnett-Ohori](/t5/user/viewprofilepage/user-id/5583025)

In terms of storing this value on the ticket you could use an automation rule such as below:

* Trigger: Field value changed
  * Field: Rule ID
  * Operations: All
* Condition: Issue field value
  * Field: Rule ID
  * Condition: IS NOT EMPTY
* Action: Comment issue
  * Content of comment: <https://website.com/{{issue.Rule> ID}}/fakewebsite

You could replace the action with "Edit issue" to put this into another field called "URL" or something else.

In terms of *creating*a website, you'd be looking at WebHooks and you'd need to discuss with your website vendor etc. on how this would work.


Tags: cloud

jira-service-management

jira-service-management-cloud
Applying Security/Restrictions to Attachments in Jira
Asked by Purnendu Chavan:

Hi Atlassian Community,

I'm looking for a way to apply specific security and restrictions settings to attachments in Jira, independent of the issue's permissions. Here's my scenario:

* **Groups:** Group A and Group B
* **Issue:** Both Group A and Group B can view the issue.
* **Attachment Permissions:** I want only Group A to be able to view and edit the attachments, while Group B should not have access to these attachments.

Is there a way to configure Jira so that only Group A has permission to view and edit attachments, while Group B can only view the issue without access to the attachments?

Thank you for your help!


Answers:
author: Nikola Perisic
body: Hello [@Purnendu Chavan](/t5/user/viewprofilepage/user-id/5112254)

You can apply some certain permissions for attachments:

* For creating, delete attachments and delete own attachments permissions should only be granted to Group A
* For both teams in order to view the issues they need to have the Browse projects permission which is necessary to see the issues

Natively in Jira, you cannot limit only attachments to be shown to the specific group because they are part of the issue. It's either shown to both groups with the limited permissions or none.


Tags: cloud

jira-service-management

jira-service-management-cloud
Automation rules and who can edit.
Asked by Myles Boyd:

In our setup, we have various JIRA admins, most in different departments to the JSM admins, how do I prevent JIRA admins accessing JSM?

I was setting up an automation and when to change

Who can edit this rule?

the only options open to me was

All admins

All admins in this project and all Jira admins.

I dont want Jira admins editing things in JSM.


Answers:
author: Ashok Shembde
body: * **Jira Administrators**: Typically, only Jira administrators or project administrators have the ability to create, edit, and manage automation rules. They can access the project settings and configure global or project-specific rules.

* **Project Administrators**: In some instances, project administrators may also have permissions to manage automation rules within their specific project, depending on the Jira instance's configuration.

* **Advanced Roadmaps Users**: If your Jira instance has Advanced Roadmaps (formerly Portfolio for Jira), users with the necessary permissions might also create or edit rules that impact how work is planned and visualized across multiple teams and projects

comments: author: Myles Boyd
body: So I can't prevent JIRA admins from editing JSM automations?

That's quite a compliance issue


Tags: cloud

jira-service-management

jira-service-management-cloud
How to easily track customers comments?
Asked by Ellie:

Hey!

I am looking for an easy way to see when a customer has added a comment to a ticket. We have over 600 tickets in the system, and since the customer cannot tag the service agents, it is a manual process at the moment of checking.

The main workaround I have found is by watching the tickets, but I want other managers to be able to see the list and reply as well,

What are ways have people managed this?   

TIA


Answers:
author: Christopher Yen
body: We send notifications to the assignee when a customer comments but something else that helps is when the request or incident requires customer input we have the agents use a "Waiting for customer" status and an automation that reverts it into "In Progress" when a customer comments on the issue. We also have an automation to remind the customer the issue is pending their input after 3 days in the waiting status.

This is the rule we use to revert the status to In Progress when a customer replies, this helps agent just to focus on all the issues that are new or in progress.

![2024-09-03 20_52_43-Window.png](https://community.atlassian.com/t5/image/serverpage/image-id/345424iF202769A3FC2B15F/image-size/large?v=v2&px=999 "2024-09-03 20_52_43-Window.png")

do your managers want to monitor activity on all issues or just higher priority ones? You can always automate adding managers as watchers on specific issues. We use a combination of System/Service, Impact, and Severity to determine if some service owners should be added as watchers.


Tags: cloud

jira-service-management

jira-service-management-cloud
Do I need to add all of our staff as customers in JSM so that they can submit tickets via email?
Asked by daniel_sayo:

We are setting up Jira Service Management in our organization. A concern is how we can easily allow all our staff at our organization's domain, i.e. irri.org, to write email to the designated email address of JSM, e.g. support@irri.org, without the need to have each staff registered as a customer user in JSM.

Is this possible? If not possible, what is the best approach to quickly allow all our staff (roughly 1000 people) to email support requests?

Thanks, looking forward to your answers!


Answers:
author: Naveen Suneja
body: Yes ,that's possible. You just need to add your [Support@irri.org](mailto:Support@irri.org) ID under email request in Project Settings.

comments: author: Naveen Suneja
body: just need to make sure that your Support ID should have license assigned, and added in email request under project settings.

![Screenshot 2024-09-03 152819.png](https://community.atlassian.com/t5/image/serverpage/image-id/345221iB6FECD602E2A3E90/image-size/large?v=v2&px=999 "Screenshot 2024-09-03 152819.png")


author: Seon Shakespeare
body: Hi [@daniel_sayo](/t5/user/viewprofilepage/user-id/5522883)

Welcome to the community!

You don't need to add all your staff as JSM customers. They can email requests to your support address (e.g. [support@irri.org](mailto:support@irri.org)) even without an account.

Just make sure "Email requests" is enabled in your JSM project settings.

While staff *can* email without accounts, it's best to encourage them to create one for a smoother experience (they'll be automatically recognised as reporters and get reliable notifications). Here's some helpful docs:

* **Adding customers:** <https://support.atlassian.com/jira-service-management-cloud/docs/add-a-customer-to-a-service-project/>
* **Account creation through email:** <https://support.atlassian.com/jira-service-management-cloud/docs/create-new-accounts-through-email/>
* **Bulk importing customers:** <https://support.atlassian.com/jira-service-management-cloud/docs/add-customers-in-bulk-to-your-service-project/>

Hope this helps!


author: Jovin
body: Hey [@daniel_sayo](/t5/user/viewprofilepage/user-id/5522883)

Depending on your Access Settings you do not need to do this. You can allow them to self-create their profile and restrict it to certain permitted domains (e.g. irri.org).

In this case, when they email the support email the ticket will be automatically raised and they can continue to reply to emails to add comments, or when they first create their account officially, they'll be able to see their historic tickets too.

<https://support.atlassian.com/jira-service-management-cloud/docs/change-global-customer-permissions/>


Tags: cloud

jira-service-management

jira-service-management-cloud