Alex Koxaras -Relational- Community Champion

@Evgeniy Gatsalov "Nothing works" doesn't really help us solving your problem, is it? Care to explain a bit the "nothing works" sentence? Do you get an error message? Do you see anything happening? I'm sorry that you are having such a lousy experience with Jira, but most likely you are unfortunate, since Jira is…

@Akil Official self transition is a part of a workflow, not Jira automation. You could also do this with Jira automation. In this case * Add a manual trigger * User a lookupissue component and find all issues you want to copy the field * Add a branch rule for the lookup issues * Edit the new custom field and add as value…

Hi @NSEU DevOps If your requirement is to allow only X number of people to create an issue, then why you don't place a validator on that specific request type, that only "members of a selected group" are allowed to create this issue? And if you have solved already the above and you want a user field that will allow only…

On cloud, dynamic filtering isn't so much "advanced" as it is on the server. You could try using Scriptrunner's enhanced JQL but you would then have to "sync" the "dynamic" scriptrunner field to a jira filter and then use it on your kanban quick filters. However, once you sync a dynamic scriptrunner filter, this becomes…

@Sreenadh if you create a custom approval, you will not have the benefits of Jira's built-in approval (like approving from the header of the portal and email) etc. I recommend to use what Jira offers and then instruct/train your users to work with that.

Kindly mark my answer as accepted in order to help others! Thank you!

Double check that the values you enter on edit issue component are correct. E.g. issue.Start date is different that issue.startdate. This will result in entering a null value => 0.

Then you are here -> https://developer.atlassian.com/cloud/jira/platform/rate-limiting/

@Akil Official you can create a self transition on your workflow(s) and the add a post function to copy the fields. For this action you might need an app such as JMWE, JWT, JSU

And here as well you can find all the plans for Jira https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/

Hi @Dason If you are talking about automation limits, then this page has them all https://support.atlassian.com/cloud-automation/docs/automation-service-limits/#:~:text=100%20emails%20in%20a%2024,daily%20or%20hourly%20processing%20limit.

Hi @Umar Maroof This requirement of your was a nice exercise for me! It was a bit tricky to accomplish that, but everything turns out great! You can create the following rule which I'll explain just below: When the Due date for a task issue type is changed, then Start Date and Due Date of all subtasks to that task will be…

Hi @Jonathan Kerr and welcome to the community, Sorry for asking, but are you on cloud on on premise? Are you talking about advanced roadmap, or roadmap planner macro on confluence? The tags you have chosen during the creation of this post, along with what you write on your post, is a little bit confusing.

Hi @Kris Grant On cloud you can't do that.

Hi @Wroblewski, Arkadiusz and welcome to the community, Do you want to know if there is a way to get the values/words from a text field to the labels field? 

Hi @Akil Official Unfortunately you can't change it. What you can do is to create a new field and then copy the values from all issues of the old field, to the new field.

@Indi J nice! Let me know if that helped achieving what you wanted!

@Robert.Ogden sorry for asking the previous question. :/ I did try myself to move issues, and inspite of having created a same CF, the field was set to be removed. After that, I've found out this open issue https://jira.atlassian.com/browse/JSWCLOUD-17437 which describes the problem you are facing. And unfortunately this…

Question: Have you added these custom fields to the screens of e.g. the story?

Hi @Robert.Ogden and welcome to the community, According to the documentation, as and you well stated: Custom fields: If you use custom fields in your team-managed project, a Jira admin needs to recreate the fields and add them to screen schemes and field configurations in your company-managed project. Custom field data…

Assets (previously known as Insights) is a CMDB app which now can be found as a built in feature on Jira Service Management Premium. So you have this "functionality" when you are on a premium plan. But if you go back to a standard plan, then you lose access to this. More about it…

Hi @Chris Rollins This happens because the category field is not in the Epic screen. * Go to project settings * Issue Type * Locate and Click Epic * Drag and drop "Category" field from the bottom right corner, to your context fields * Click Save Changes * Try again Let me know if that worked for you.

Ηι @[deleted] and welcome to the community, As @Christof Cuypers well stated, the premium features will be disabled. E.g. the calendar will not be visible any more on your instance. Assets as well. So if you base your work on Assets, then yes, your work will be disrupted. If you base your work on feature that can be found…

Hi @Gary Spross My instance works fine and I dont encounter any problem at all. Concerning the status page, keep in mind that Atlassian usually (to my knowledge) raises an incident after a while and not at the exact time of the incident. So if there is a problem on there part, they will post in a while. Best thing to do is…

Hi @Steven Johnson You can get that if you write this: {{#issue.summary.split(" ")}}{{left(1)}}{{/}} And if you want to get exactly what you wrote on your question, then type this: [{{#issue.summary.split(" ")}}{{left(1)}}{{/}}] The above will get you the acronym of the parent task in square brackets. If e.g. you have a…

@Manoj Yes, scriptrunner will work just fine. You just need to create a new "Job". Take a look at the following and keep in mind that some scripting will be necessary: * https://library.adaptavist.com/entity/automate-the-creation-of-an-issue-in-jira *…

Hi @William Glover There is no way to remove these add-on users from the list. Not one that I know of at least. The users are not in the assignee list most likely because the add-on users group do not have the assignable user permission. You can view and watch this issue https://jira.atlassian.com/browse/JRACLOUD-69084…

Read also this post as well https://community.atlassian.com/t5/Jira-Software-questions/How-to-make-an-automation-rule-trigger-in-a-time-period/qaq-p/1543966

If the scheduled period is known and fixed, you can use Jira Automation with the Schedule trigger to create a specific issue type, with pre-populated field and assigned to a specific user. Read more here https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/ And the add the Create Issue…

Hi @Manoj You can't create a future issue in Jira. You can however create an issue with a date field in the future. E.g. create now an issue and placing a due date on the future. This is doable. However what is the basic need behind your request?