Mikael Sandberg Community Champion

@Céline - Maestrel @Without an app or using my form workaround it is not possible to “hide” a field on the portal.

@kevin.deadman You need to click on the transition (the arrow leading into the Done status), not on the status itself. then add a rule that updates the resolution field or show a screen that have the resolution field on it.

Hi @Tim Rundblade, Welcome to Atlassian Community! All training that you find on Atlassian Learning is free, and the certifications are $100 for ACAs and $249 for ACPs. 

Hi @TheKeiron, Welcome to Atlassian Community! Please report this to https://www.atlassian.com/trust/report-abuse and the they will take action on this. 

Hi @Denner Dias, Welcome to Atlassian Community! This is a known limitation, and based on this suggestion, JRACLOUD-69295, Atlassian at the moment is not intending on implement a solution for it.

@Darryl Lee Yes, I agree that it is a bit of a long way of displaying the data using a Form. But because you are using the submit action the form becomes a read-only form on the portal and only the agents can re-open the form, There is an option to lock the form, but the you would need a project admin to reopen it, and you…

Hi @Steven Koolen, In the approval part in the workflow, are you excluding the reporter by any chase? Or does your automation prevent you from adding the reporter as the approver? One way to automatically approve the request if the reporter is also the owner is to compare the two fields using smart values. For example you…

@Céline - Maestrel I just published this article showing how you can accomplish this. Hopefully it explains what I tried to convey above.

And the field you want to add only has to be on the work item view, you do not have to add the field to the request type view when using a form to display it. As I mentioned above, I had one project that wanted to display a message field every time that it was updated, and by adding it to a form with a field linked to that…

@Céline - Maestrel I have tried and was able to attach multiple forms to a work item/request type. Once the work item is created you can attach more forms if you like, you are not restricted to just one form per request.

Hi @Hubert Aerts Welcome to Atlassian Community! The closest would be to use Category under Project settings > Details. You could then filter your projects based on the category in JQL and on the View all projects view.

Hi @Rosetta Hayes, Welcome to Atlassian Community! If you are asking about who can create canned response templates, you need to be project admin in order to do that. If you are asking who can reply to the customer with a canned response then the answer would be that anyone that is an agent in the project can do that, as…

Since you are triggering on an action that edits a work item you can use the {{changelog}} smart value to see what the previous value was.

Yes, it can be done by using work item security schemes. Once you created a scheme you can set the work item security level either manually or via automation.

Hi @TheresB I can only notify the support team one time per question, so the only thing I can recommend is that you either wait on a response from @Mark C or create a new question.

Have a look at this article that I wrote about assigning tickets based on the time of day.

The main difference is that Public Forms have access to all work item fields, and you can rename the fields, for example instead of seeing Summary you can rename it so the user sees "How can we help you" or something else.

Okay, what I would do is add a Log action to verify that {{issue.customfield_11322}} has a value or not and then go from there.

@Maciej Dudziak _Forgappify_ question for you regarding the app. Is the "Linked Issues Validator" run after the user clicks the submit/transition button, or does it prevent you/not showing the transition until the child work items are fulfilling the condition?

Hi @vid_ribic , Welcome to Atlassian Community! I have notified the Atlassian support team that is on here, they will reach out to you within 2 business days to get this resolved.

Hi @Mehrdad Sadraei Welcome to Atlassian Community! It sounds like the Due date is a required field, and that is why you get the error. Have you tried adding the date to the custom field? It could also be that the due date is not on the screen/layout so you do not see it, but still set as required in a project…

Hi @Jyoti Patel, What you are looking for is a condition, not validator. Conditions prevents users from transition work items if the condition is not fulfilled. Out of the box Jira only have a condition that can block the transition depending on the status of sub tasks. In order to do it based on issues linked to an epic…

Hi @Jessica Ketcham Welcome to Atlassian Community! Are you using the new UI or the old one? The new UI is moving everything to the left, and in the new UI the Link work item has moved to the + Add button at the top when you are in the issue view.

I would check with your Atlassian site admin/IT department. It sounds like they have configured authentication policies, either in the IdP your are using and/or on the Atlassian side.

To set the assignee based on a text field you can use that to find out the Atlassian Id by doing a web request to Find users endpoint, the result will have the Atlassian Id in it. Once you have that then you will use the More options and the Additional fields area to set the assignee like this: { "fields": { "assignee": {…

Hi @Katie.Gilbert, Welcome to Atlassian Community! The custom field that you are using to set the assignee, is that field a user picker field? Or is it just a text field? In order to set the assignee you need to use the Atlassian Id for the user unless the other custom field is a user picker one.

View restrictions are not per page if you use parent/child hierarchy, only edit restrictions are. Another way of doing it is to set the space permissions to be more restrictive. But if you really want to restrict access to pages that are not yet ready for a wider audience you may want to look at an app in the Marketplace…

Hi @Bee Ivey, Welcome to Atlassian Community! You could use view page restrictions, you can then restrict who can view to only admins and the owner of the page. Once it is ready to be shared you can remove the view restriction. Note that view restrictions are inherited, so if your page has child pages then they would also…

Just to add to this, if you are using the new editor you have to switch to the old one before you can go to Text.

Correct!