Alex Koxaras -Relational- Community Champion

Yes! That's the one. The one who is not receiving the email

Hi @Naama Betzalel Have you already took a look at this? https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/ and https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/

Hi @Bhagavan Goud Refresh your screen and clear your cache. Try from another browser as well as from an incognito window. If the problem persists and you are on a paid plan, contact Atlassian's support.

Hi @Touqeer Anjum You have to see if that user has project membership for that specific project and if that membership provides the basic permissions (brose project permission). In addition check if any security level applies. 

Now that I'm thinking of it, you could use script runner's behavior to change default values and hide the field from any request type. Do you have this app installed?

If you are using the same issue type for X request types, then no. To all these X request types this field will be visible and applied with the default value.

Hi @Simon Rose and welcome, You mean changes to jira itself, like workflows, schemes, configurations etc?

Hi @Chandrasekhar P I think that you should contact Atlassian directly about this. Not many things can be done from the community. But I'm curious... even if you choose a site to authorize the app, it's still greyed out?

Hi @Lindsey Monyelle and welcome to the community. Out of the box, Confluence doesn't have something similar. You could search the marketplace for an app that could do a similar task.

Hi @Murtuza Dudhiyawala Request types on JSM are bound to only one issue type, meaning that the build-in email handler of a JSM project can be associated with only one request type and consequently only one issue type. There are some other workarounds to this: * You can setup a different email handler (out of this project)…

@Łukasz Gut if you have read the tempo documentation, you could easily find out that you can only add the ACCOUNTS field on your issues. The way tempo works is that you have your customers and for these customers you can have multiple accounts. E.g. * Customer A (customer)* Customer A billable (account) * Customer A non…

@Rilwan Ahmed if that field appears on the rest of the request types, this mean that all request types are using the same issue type. So field context will do nothing.

Hi @Shaily Bajpai and welcome to the community, We could try to help you, if you could provide us with more details: * Are you on server or cloud? * Do jira members come from an active directory? * How do project memberships are given? * Did your project admin take a look at the logs?

Hi @Łukasz Gut and welcome to the community, What exactly you mean by "add ACCOUNTS" to your issue? You mean populating a field with a value? If that is the case, then you can't do what you ask for. If you were on server that would be possible with scriptrunner's behaviour. In cloud currently, behaviours are not supported…

Hi @Mohamed Saad Taha You have to create request types using different issue types. For these issue types you have to to create separate screens and screen scheme. In these screens you will choose all the necessary fields. Doing all the above will result in having different fields for your different request types. Read…

@Jesper Fransson sorry, but as I told you, the preferable way doesn't exist on Jira. I mean Jira can do a great deal of things, but Atlassian can't satisfy all people's need. And that because how Jira works currently can't support this. Now, onward to a viable solution! What I thought is that you could use Forms for that…

Hi @Kai Ytterberg and welcome to the community Text methods do not apply to single select fields. That's why you are getting null. You should first place your value on a variable and then do your expression. Mine works like this: And I get proper results! Hope that helps :)

Hi @Jesper Fransson No, you can't do this in Jira with out of the box functionalities. What you could do is to experiment with multi picker fields, such as multi-user picker which allows you to select more that one use. The other fields what are they about?

Hi @Manjula Jayaprakash and welcome to the community, By default confluence is an open space and as such, if no modifications take place by the confluence admin, you will have access to your personal space to which you can add page restrictions (meaning that no one but you will be able to view or edit pages). Further more…

Hi @Xiuxiu_Li and welcome to the community You have to contact your project and jira admin of your instance for that matter. Most likely your jira admin didn't include the attachment field on the request/issue type. Editing comments is a permission that you have to be given by the jira admin. You have to speak to your jira…

@Jaime Netzer thanx for sharing this! I'm not yet Atlassian Certified and I currently hold two certifications. Hopefully by the end of the year I'm planning to get the third one!

Hi @Marc Bornstein and welcome to the community. With all the out of the box functionalities, I think that there is no solution to your problem. My best guess would be to find an app from the marketplace which would provide a Cumulative flow diagram widget for the dashboard. Then create a shared dashboard with all the…

Hi @Richard Morgan Queues restrictions are not possible. Not in that specific sense. * However you could apply an issue security scheme with certain security levels so as to distinguish which issue your team can view, and which issue can be viewed by the other team member * Set the corresponding security levels to all…

Hi @Rob I don't think that it's possible on TMP. https://support.atlassian.com/jira-service-management-cloud/docs/set-up-request-types-in-team-managed-projects/

Hi @Subgerencia and welcome to the community, What exactly you mean change it? If you are using the native log work from Jira, then if you project/jira admin has given you sufficient rights, you can edit your worklogs. If you are using an app, you should check if such rights exists. If they do, then you have to have…

Since you tried as well clearing your cache and still nothing, then, besides contacting Atlassian, I would suggest to ask another colleague of yours if they are facing the same problem with you.

Congratulations @Jack Brickey !! A well deserved celebration and recognition!! Here's to another 5, 10, 15 more years of being an active member of this community, which wouldn't be the same without you!

Hi @Cornelius Schiffer Can you try to create a new variable after that lookupissues and assign the value of {{lookupIssues.Notify on Release.distinct}}. Then call the distinct method on the new variable. Log it and see what this yields.

Can you try to log time on an issue using the native method and see what's the reaction of the rule? Does it work properly?

@Vikrant Yadav hi! Did you try the following?