Kevin Johnson_3sxc8m Community Champion

Sadly, I don't think this feature is possible in Bitbucket Cloud, you can only restrict write access and merge via pull request by users and groups. -Kevin.

Hi @Ramanathan Hariharan , If you are trying to get issues that are not task or subtask try something like "issuetype != Task or issuetype != Subtask" If you want all issues other than both try "issuetype not in (Task,Subtask)" Error is due to the issuetype not mentioned, you cannot give the value continously. -Kevin

Sure, hope the same

Hi @Bud Herz , project = FS AND issuetype in (Bug) AND Sprint in openSprints() and Sprint not in closedSprints() This should get only the bugs added in the current active sprint, not from the old sprint. Hope this helps. -Kevin.

Hi @Nirav Damania , Did your issue resolve? -Kevin.

As I have mentioned above try to choose the custom field value and use "==" to check equals. I'm not so sure how find({""value:}) works.

Hi @pini mari , Was the problem resolved? -Kevin.

Hey @Iana , Happy to tell you that after few attempts, I was able to figure out a solution. Attaching the pictures below for your reference. Please replicate the same to "Copy custom field value from an Epic to Story when a Stroy is created". Hope it helps. -Kevin.

I did some background research on this, came to know that is it an issue with confluence. Here is the link to that issue: https://jira.atlassian.com/browse/CONFSERVER-55928 . The fix is about to be released. Hope this helps. -Kevin.

Here is a link to the details of all even in the notification. Link: https://confluence.atlassian.com/adminjiraserver/creating-a-notification-scheme-938847330.html As far as I have known the issue updated event includes everything, every small change in details of an issue. Hope this helps. -Kevin.

Yea, I see that, but it is not supposed to work that way, in Nextgen project when an issue is moved to the Done column, the resolution is set to Done by default. I tried searching for a related doc or issue, but I couldn't find one, I suggest you contact the Atlassian support team for a better solution. -Kevin

Hi @shravya chinthapatla , Here are the documents that states how you can share the dashboards and filters with other users. Filters: https://support.atlassian.com/jira-cloud-administration/docs/manage-shared-filters/ Dashboards: https://support.atlassian.com/jira-cloud-administration/docs/manage-shared-dashboards/ Cheers,…

@Jimmy Seddon hahaha got it, it's really innovative that how the community badges are designed. Well, then it's time for me to regularly and actively participate in the community. Hope I'll keep up my work. Should we still be waiting for the Friday-fun backlog to drop or are there spots available? -Kevin.

Hi @Jimmy Seddon , Thanks for your reply. I have already read through the above-mentioned article, but it is not so clear, and badges like group hug I'm not so sure, will it take some time to achieve rather than being instant as other badges? Regards, Kevin

@Jimmy Seddon Inspired by your decision-making skill to take a strong move in switching company in spite of this pandemic situation. Hope you're doing well now. Cheers, Kevin.

I think you have mistaken me for the Atlassian support team, I'm a same normal user as you are, I don't have any special option to access your project and check. For sure there is a problem with the Workflow validator or you're field configuration, kindly share a full picture of it so the community members can help better.

@John Funk True and it is not a good practice to bring back a completed story with completed subtasks to the backlog and delete it later.

@Yvonne Wan Try choosing the Epic parent issue as you're trying to update that, and not a normally linked issue. I'm attaching this picture for your reference, try something like this.

so how is the automation set up to delete the sub-tasks, can you share a picture or explain on that part.

Hi @Dave Gough , Sadly, I don't think that is possible as of now to pin 3rd party fields in the top of context fields. Regards, Kevin.

Please make the Priority field mandatory which is only needed and try removing the other priority from the screen. If this doesn't work please set both the priority fields not as mandatory and check if you still receive the error, if you don't receive the error, then set the priority that is only needed in the screen as…

Hi @Iana , Here is an example of how to implement your requirement. https://community.atlassian.com/t5/Jira-Software-questions/Copy-field-value-from-Epic-to-child-issue-with-automation/qaq-p/1421943 Cheers, Kevin.

Hi @Jeevaranjan , Unfortunately, this feature is not possible with the default Jira configs. There's not an event to trigger when the scope of a sprint changes, so it cannot be notified via email. Regards, Kevin.

It seems the priority field is a custom field, is the Priority system field is also mandatory in your field configuration?

It cannot go wrong and throw an error magically, kindly check whether you have set any validator in workflow, Field configuration for the mandatory fields and if there is still an issue kindly explain your project set up and provide the details about fields on your screen. Regards, Kevin.

@Gabriel König "Issue Updated" covers all issues which have had their details changed that includes Editing an issue, changing the summary, deleting a comment, attaching files to the issue, linking an issue, etc. On disabling this all these updates will be stopped. Regards, Kevin.

Hi @pini mari , Is there any field called urgency or priority? if so it might be a mandatory field, that field data has to be entered in order to create a task issue. Regards, Kevin.

Hi @Gabriel König , As it fires the Issue updated event disabling that will also stop other updates regarding that issue. Unfortunately, as the feature is not fully developed and notification scheme is provided by Jira there's no workaround. Regards, Kevin.

Hi @Marcus Möhrmann , Sadly, this feature is not possible at the moment. Heres a ticket related to this feature, you can vote on it if you're intrested. Link: https://jira.atlassian.com/browse/JSWSERVER-16256?error=login_required&error_description=Login+required&state=da4ebe8b-ce45-4f58-bdf0-65fdf4f43a11…

Hi @Parthiban Sekar , You can create a workflow transition and set an Automation rule that will create a subtask and assign it to a certain user for each issue that passes the transition and you can bulk transition the issues. Once the process is done you can remove the transition from the workflow. Hope this helps.…