Jack Brickey Expert

The customer will be able to see all "public" comments in the portal. They should not see "internal" comments. There isn't anyway to prevent the customer from seeing public comments in the portal and expect that is not desirable.

I have never experienced this. Here are the steps I would suggest: * test with a different project * check with other users to see if the experience the same * check if the admin can edit the work log * if all of the above fail reach out to Atlassian Support. It may be a bug. if I think of something else I will add. If you…

Hi Sofia, see if this article helps - configuring-issue-level-security 

Hi @ng-parth , the only way to change your domain for cloud is they Atlassian Support and it appears you have been directed here which means that you either have the free or starter license. Atlassian doesn’t provide support thru the official support site for those licenses. Can you confirm your license type is one of…

What are the details of the send email action? Have you checked the email logs?

And the work that was logged is of your own doing?

Hi Rose, the way Jira service desk works related to emails is that if an agent or customer responds via email then it will be public. If the email comes from a JSW collaborator for the service desk project then it will be an internal comment.

My guess is that it is not supported in Server. :-(

you either haven't published the workflow or you have not associated it to your project/issues.

if you have a specific Epic you can use this... project = ABC AND "Epic Link" = ABC-33 OR parentEpic in ("ABC-33")

You need to ensure they have Browse and Create issue permissions in the project. I assume these users have a JSW user license?

I would inspect your board’s filter. I suspect that the filter is specific to your old workflow. 

I would recommend JSD for that purpose. While there are many reasons for this one key one is that your internal customers will not be paid user licenses only the agents working the issues will require a paid license.

On the board if you have ellipses in the top RH corner there is a Print cards option. Is that what you are using and it is not meeting your needs?

You should be able to achieve this using Bulk edit. Create a JQL filter that captures all of the issues you wish to update and none of the issues you do not want to update. Click on the Bulk change under ellipses in upper right. Select Edit issues and go thru the screens until you get to the list of option and find…

Try fixversion is Empty

Here are the highlights, you can find details of each step in the docs. * create custom field - Jira settings > Issues > Custom fields > Add custom field > multi-select. Here you will add all of the names of those that may review/approve. Give the field whatever name suits you, e.g. “Approvers”. * create screen including…

Hi Phil, At the risk of conveying knowledge you may already be aware of, you don’t monitor boards in Jira, rather you monitor the issues underlying. You set up notifications on updates of issues. You configure notifications under project settings > notifications. This includes Create issues. if I am missing your request…

Raymond, it is unclear what your question is and how it relates to the original issue. It appears you are having a licensing issue. You may wish to contact atlassian support

I don’t even know of any addon for cloud instances. Thought you may find this article helpful. linking-issues 

Generally it is used to define which product release version(s) the issue is addressed in. Often it works in conjunction with Affected Version(s). For example affected versions: 1.1, 1.2, 1.2.1 fix versions: 1.2.2, 1.3

That would be the project key. While it can be changed it will change for all issues in the project. Assuming that is what you want... project settings > details and change the Key. note you need to be an admin.

Here is an approach that comes to mind. There may be other (better?) options. I would create a different issuetype for one of the teams so that they can have a different workflow, screens etc. you could even use the issuetype to move the issues from the backlog to the other team, removing the need for the Team custom field…

Hi @Sobhy Admin and welcome to the Community. I will start by conveying that I, like most folks in the Community do not work for Atlassian. I say this only to avoid early confusion as you seek help here. Any Atlassian employee will have the “Atlassian Team” badge in their name. with that said, let’s get to your questions.…

There is a lot of docs on boards here is one but I recommend you search the support site for more. https://confluence.atlassian.com/jirasoftwarecloud/what-is-a-board-764477964.html 

@neelam annad , I would be interested in hearing more on this. I am not aware of “releasedate” being an available field in JQL. The only option for fixVersion in JQL is either a specific version or releasedVersions() or U.N. releasedVersions(). Maybe “releasedate” is a custom field in your project or possibly something new…

Your best (?) option would be to create a user picker mult-select custom field. This will be a controlled list of users that must be added when adding the list but it is better than a text field since it is controlled. Of course you could make it a text field and instruct folks on how to add names (formatting). But you…

You might check out Issue Level Security to see if it will meet your needs.

what do you mean by "prefix"? Is this in the Summary field or something and you are trying to change all occurrences of PS to PH? The bulk edit doesn't support this. One thought would be to export them to CSV, change them in Excel and re-import.

DOH! just as soon as I hit enter something occurred to me that I did wrong. Here are the actual steps that achieve your goals. 1) you use "Time Spent" field for Field Required validator 2) you use "Log Work" field for the Screen that you create NOT Time spent sort of confusing names to be sure. I hope this works for you!!