Gor Greyan Expert

Dear @Line Veronika Nielsen Jira Service Management does not allow you to show additional fields on the customer portal after the ticket is created unless those fields are already part of the Request Type.

Hi @Line Veronika Nielsen Welcome to the Atlassian Community! The fields that customers can see in the portal are controlled by the Request Type configuration, not directly from the issue view in Jira. For that, go to Space Settings. Choose the Request Management --> Service Request There you will see the Request Types.…

Hi @Minh Tran Duc Thanks for the question. Please have a look at this doc, it can be helpful. https://support.atlassian.com/subscriptions-and-billing/docs/switch-from-monthly-to-an-annual-subscription/

Dear @Tudor Tofan Yes, thanks, it is also working one. I provide an advanced version, to become advanced :)

Hi @Yahya Aliyev Thanks for the question. Your rule is creating duplicate subtasks because each branch is iterating over multiple issues. In your case, both “For: Current issue” and “For: Children” branches are causing the automation to re-run the “Create Sub-task” action for each created Story, which results in the same…

Dear @CloverYang I did research and found out that for team-managed projects, it is impossible to set a validator for the Worklog. See this article, where a workaround is being suggested.…

@CloverYang Mine is Company company-managed project. Did you try to write the full name? Time Spent

Hi @CloverYang Thanks for the question. Did you try to write Time Spent there? I tried, and the field is being displayed.

Hi @ethiruma You are very welcome.

Hi @ethiruma No, Jira Cloud’s REST API can’t create a story and its subtasks in a single request. You can have a look at this, which explains how you can do that. https://stackoverflow.com/questions/54431205/jira-api-create-issue-and-subtask-in-a-single-api-call?utm_source=chatgpt.com&newreg=5a94ff27768b4a699216de7320b4c6ff

Hi @PLaksh11 Thanks for the question. As I know, natively, Jira Cloud cannot delay a workflow transition or a post-function. I think you can instead use an Automation rule, for that purpose. Also, I found this article in the JMWE app, which provides an example for a delayed post-function.…

Hi @Shahriar I could see above that @Bill Sheboy provided the solution. That's great, thanks!

Hi @Mathijs Bouwmans I will tag a colleague from the Atlassian Team. @Karan Sachdev , please have a look, if you can help here also?

Hi @Shahriar Thanks for the question. Try to find the customfield ID for the Target start field and use this expression. {{issue.customfield_12345.plusDays(3)}} Also, .plusDays() → adds calendar days .plusBusinessDays() → adds business days Let me know, if this worked or not.

Hi @Kaviya Ragavendrasamy Welcome to the Atlassian Community! Jira Cloud provides both a 30-day trial and a free-forever plan, and they work differently: - 30-Day TrialWhen you first sign up, you get a 30-day free trial of the Standard or Premium plan.This lets you try the advanced features before deciding whether you need…

Dear @Bisi Ade Glad to help.

Hi @Bisi Ade , Welcome to the Atlassian Community! Try this one, it works on my side. issuetype = Epic AND statusCategory != Done AND issueFunction in linkedIssuesOf( "issuetype = deliverable AND statusCategory = Done")

Hi @my.fsddesignstudio Thanks for the question. Were you using a paid Jira or a Free Jira subscription plan? If you used free subscription, and it had no activity for 120 days then the product is deactivated, which is stated in this documentation.

Hi @MARTIN-GONZALEZ Victor (Extern) I think you’ll need to contact your company’s Jira administrators or IT Help Desk to get access to the VPM project. They can verify your request and grant the necessary permissions.

Hi @ltammineni Welcome to the Atlassian Community! Did you check if the user was added to your organization? Also, check the license count in the Administration → Billing → Manage subscription section. If the above-mentioned is okay, I suggest opening a ticket on Atlassian Support. https://support.atlassian.com/contact/#/

Hi @shashikant wadhai Welcome to the Atlassian Community! What error message do you recieve while trying to log in? Please provide any screenshots of the restriction in order to be able to help.

Hi @Jeffrey Bistrong In Jira, the rule actor is fixed per rule (“Automation for Jira” or a specific user). It can’t be changed dynamically to “the current assignee.”

Dear @Periyairusagounder, Sathiya Please add that permission to your user and you will have access.

Hey @Periyairusagounder, Sathiya In the project's Permission scheme check the Move Issue permission. It is missing for you.

Hi @Periyairusagounder, Sathiya Yes, you can move the sub-task to another parent, using the Move feature. See the attached screenshots.

Hi @Rasmus Hvilshøj Yes, seems it was changed recently, as it is also the same on our side. Yesterday, another community member stated this. Hope the change will be reverted back soon. https://community.atlassian.com/forums/Jira-questions/Active-Sprint-view-always-grouped-by-stories/qaq-p/3142565

Hi @Vladislav Sinkevitch Welcome to the Atlassian Community! There can be different root causes, which can lead to this. Please check these points in order to understand where the issue comes from. 1. Check that the issue type you created from Slack matches what the board’s JQL includes. 2. Check that the Backlog status is…

Hi @Jayanth Glad that it helps. Also, please accept the answer, as community members see that the solution was accepted.

Hi @Jayanth Thanks for the question. You should put the date window inside updatedby() rather than using a separate updated clause. Otherwise, Jira will bring back any issues those users ever touched that also happened to be updated in the last 7 days (by anyone). Use this one. issue IN updatedBy("gor.greyan", "-7d")…

Dear @Iris Andersen Glad to help.