John Funk Community Champion

You are trying to copy it from a "Parent" issue but you haven't really established a "Parent" you just have linkages. You should probably create a branch associated with linked issues prior to the field update.

Not that I am aware of. @Bill Sheboy - Thoughts? 

You have to edit the workflow itself - not the automation. Got to Settings > Issues > Workflows Search for the workflow being used by the project and click on Edit It might be a workflow specifically used by sub-tasks so be sure you have the right workflow. Then click on the transition to Done. Finally check the post…

You can certainly add additional custom fields. You will need to be a Jira Administrator to do that with Company-managed projects. Go to Settings > Issues > Custom fields For Team-managed projects, you will need to be an Administrator on the project and then you can create custom fields directly in the project. 

Hi Angelica, The nature and purpose of Team-managed (formerly Next-gen) projects is that they are independent of all other projects. So what you are hoping for cannot be done with Team-managed projects. You will need to use Company-managed projects. 

Hi @it_marcapo - You would probably need to create a custom date field that captures the value of the date when it is moved to XY status. Then you would be able to compare the dates using Automation. 

So which field is not showing up for you? 

Hi Eric - Welcome to the Atlassian Community! You can do as guided by @Prince Nyeche - ELFAPP - that should work well. But I would caution you on deleting any issues in Jira. It is better to just leave them as Done so they are searchable in the future if needed. You can exclude Done issues from boards and filters so…

Yes, you would need a separate workflow for Bugs - OR - you can use an add-on like JMWE where you can do conditional validators. :-) You could just copy the existing workflow and label it as the Bug workflow and then modify that. So the process is pretty quick and easy. 

It might be related to Confluence subscription. 

You can have 10,000 users per site, but you can have multiple sites if needed. So it's pretty much unlimited in that way as well. It's pretty much whatever you can afford. I think I might have heard at Team '21 conference that the site limit might be going to 25,000 users. Projects are unlimited as Prince says. 

Hi Jerry - Welcome to the Atlassian Community! You could add a validator to each transition to require those fields. That way they can't move the card without the fields being field in. 

Roughly, how many of each of those will you need to be able to do? 

It will look like this: https://jira.atlassian.com/browse/JIRACLOUD-xxxxx

Hi Gregory - Welcome to the Atlassian Community! How would these custom fields be different than other custom fields? What type of project are you using? 

Hi Anna - Welcome to the Atlassian Community! I don't believe there is a limit - other than performance will suffer at some point. What kinds of numbers are we talking about? 

Yes, you must be a Jira Administrator to be able to submit a ticket. Can you have someone in your organization do that? 

Hi Alexey - Welcome to the Atlassian Community! That message looks like it comes from the workflow itself. Is there some type of post function on the workflow in addition to the automation rule? 

So you don't see the Sprint Number in your list to update? 

Hi @Charlotte Nicolaou - Just checking in on this. We have JSM Premium but we cannot see Opsgenie under billing at all - it is never mentioned. And on another note - do you know a timeframe for when the API will be available for the integrated Insight product? Maybe at least a rough estimate - in a month, in a quarter, end…

Hi Maja, You need to update the workflow and edit the Transition that is used to Reopen the ticket. For that transition, you need to add a post function to Clear the Resolution field. That will remove the strike-through. 

Hey @Tom - are you not able to enter a support ticket here: https://support.atlassian.com/contact/#/

Hi Eran - Welcome to the Atlassian Community! Are you using the Lite (Free) or Pro (Paid) version? Can you share the rule that you have created so far? 

Hi Vlad, Go to Settings > Issues > Workflow Schemes Then add the workflow you created to the Workflow Scheme being used by your project. Be sure to map any different issue types at that time as well. Then, finally, be sure to publish your workflow scheme changes. 

Hello and Welcome, Sixtus! We are glad you are here!!

Not that I am aware of. 

Yes

Hi Dennish, If you just give the users Browse Project permissions in the permission scheme for that project, then they will view only access to the board. 

Hey Steven - I don't know of any way that you are going to be able to change that label for the dropdown. It think it is confusing, too. But you are probably stuck with it. 

Interesting - it looks like system type fields rise to the top. Or maybe just People system type fields (Assignee and Reporter).