Jack Brickey Expert

Hi @Yoda , I'm not sure I understand the issue. Are you saying that you want to require all 4 users to approve and seeing that only one is required? If so see this article - add-an-approval-to-a-workflow . If your question is something else please let me know.

What does the history tab show on these issues. Is there an entry where the sprint field was updated to include new sprint?

Hi @Shaz Begum , I am not following here. Could you restate? I don't know what you mean by "sheet". if you want to capture notes on the issue, you could do that in the comments or you could create a custom text field.

This doesn't seem to relate to this old post. It is worth mentioning that the video is associated with Team Managed Projects as well.

Hi @Reb Bravo , you can use the Issue Assigned trigger for this. It will trigger when the issue is initially assigned as well as any subsequent updates. For this reason what I would do is add a label to the initial assignment, Such as "assigned", And then add a condition to test for the existence of that label. If it…

Hi @Peter Weigert , welcome to the community. If you are asking to change your email address for your Atlassian account, please visit this URL https://id.atlassian.com/manage-profile/email 

Hi @abhijith Ullas , do you mean ".net" here. Atlassian' cloud instances are ".net" not ".com". Assuming that was just a miss type and you are not able to access your instance could you tell me the last time that you were able to do so? Is this possibly some free instance that has been sitting idle for a long period of…

Ah, however, maybe soon... I recalled there are old requests for this and found the following that seems to indicate delivery this year. https://jira.atlassian.com/browse/JSDCLOUD-195 

Hi @Samuel Habib , unfortunately all customers will have access to all Request Types. There is not a means of adding customers to groups/roles and using those groups/roles to restrict access to certain Request Types.

Hi @Sophia Smith , a couple of editorial comments first if I may... * At the risk of stating the obvious, unless the issues are created by a system the likelihood of exact match on summary is remote. * While I am not familiar with your environment, I believe having automation alone marking duplicates is error prone. now to…

Looks interesting 

@Vijay Dadi , not sure, I understand. 🤔

Thanks for all the info Constance. I was seeing similar to what you and Darryl both mention. I think Darryl has zeroed in on the culprit and it may simply be something that isn't fully baked yet. Hopefully we will get an official answer back in this thread..

I think this is the right move for sure. Though I really haven't played with atlas other than a brief time after launch. I need major training. 😏

lucky indeed! I would love it if they had a hide option similar to how you can hide (disable) previously used values in a dropdown custom field. this allows you to retain the history but prevent unwanted ongoing usage. 

this works well if there are no existing issues with that issue type. if there are you will be prompted to change the issuetype.

Hi @Constance Hua , can you tell me where that screenshot is from exactly? Is it in the Jira app or in Community or??? If in Jira, what screen?

Hi @Frank Leest , you should be able to go into the billing section and look at the history for a given product. * click on the cog in upper right * select billing * select manage on the desired product (Confluence in your case) * select history 

Agreed. @Ly Lim , I don't understand a section in the backlog called pre-planning can you share a screenshot of this?

Ah, OK. so this is a team managed project (TMP). In that project type indeed you cannot remove those system fields. I should have indicated this previously when I provided an answer for Company managed projects.

It seems that arbitrarily setting a due date via a post function is misguided. Would you not want the user to specify?

Hi @Fatima AALLA , your first sentence seems incorrect. I think you are saying that you are trying to leverage Workflow Post functions to offset the reliance on Automation. In any event, back to your question. Could you not use the Field required validator accompanied with a transition screen requiring the user to enter a…

Hi @Constance Hua , I will escalate to Atlassian. I am puzzled by the error that is occurring. It may be that it occurs if you have not opted into the Kudos feature. I cannot reproduce but am in the program.

Duplicate post 

Hi @Lukas Hametner , welcome to the Community. there are two options to consider. if your field configuration is shared such that you do not wish to impact the other projects then you can simply remove these fields from your screens. * project settings * screens * edit each screen config and remove the fields if your field…

Have a look at this post - Restrict-Issue-Type-Creation-for-Certain-Users also search the Marketplace for "workflow validator"

So if you enter "fixversion" in the field you should get a drop-down of available versions and you should choose the version you are interested in. I use SR24515 in my example as that was what you provide in your post. You might want to zero in on your version by including your project in the JQL (change the bold to meet…

Do you mean to say you couldn't find the advanced search view? If so... * click into the search bar in the top menu * at the bottom of the pop up select Advanced search * in the query bar paste the JQL provided previously - fixversion = SR240515 * once the results are returned click on the columns icon and add Parent field 

The list view and board view don't support the same features. Too JWM and JSW are different applications and board config is indeed different. Now this might change in time given that Atlassian has announced that the two will be merged into one. regarding your last comment it would be worthwhile understanding whether the…

Now I can pass quietly. 😂