John Funk Community Champion

It looks like it thinks you are trying to create that field instead of just use that field. If you clear out the value and the click the dropdown and then start to type a few of the letters in the field, does the field come up so that you can select it? 

How are you creating the issues under the Epic? Manually or by automation? 

Hi @b.a.firas - Welcome to the Atlassian Community! if you are creating the stories and subtask automatically buy an automation rule when you create the epic, it would just be a matter of copying the reporter from the trigger issue to the assignee. If the epic already exists, and you create a new story or task, you could…

Hi @혠니혠니 - Welcome to the Atlassian Community! you can solve this a couple of ways. One is to create a filter with what you have, and then create a subscription that will email you the list of issues each day that would be the simplest way. The other way, would be to do an automation rule like you were suggesting. But you…

Hi Kris, I have wondered that myself, and I don't know. But you are also fine to do what you have done. 

Hi Filipe, If I am understanding your correctly, when the JSM ticket creates/clones an issue into the JWM project, it should link the two issues together using a rule action for Link Issues. Then you can have rule that checks for Field Value Change trigger for whatever fields you want to copy over from the JSM ticket to…

Hi Ravi, When you say "queue" do you mean a column on a board? Or do you mean an actual Queue used by JSM? If it is an actual Queue, the Queue is based on a JQL statement. You would need to change the value of a field for ticket/issue so it meets the criteria of the JQL used by each Queue. 

Hi Jiangyu, You will need to update the Issue Type Scheme used by the target/destination project to include the Issue Type that you want to move it to. 

Hi Rahul, You can get guidance here: https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/

Yeah, I think it is a bug that has been introduced. You should open a support ticket with Atlassian: https://support.atlassian.com/contact/#/

Sorry no, I did not have that trouble. Are you still experiencing it? 

I am suspicious that you do not have permissions to the Jira Software Product. 

Hi Jonas, There appears to be a bug that has been introduced. Please create a support ticket for Atlassian for them to investigate. https://support.atlassian.com/contact/#/ Also, please post the resolution back here. In the interim you should be able to change the status directly in the card. 

Hi Vasiliy, You should be able to do the items you describe with Automation Rules. If you will post your rule here and what is not working, we can try to help. 

If you run into any problems with your rule, just post it here, and we will help you. 

The status must be in the last column of the Scrum board. 

Hi Kristine - Welcome to the Atlassian Community! You should create a custom field of Select List (cascading). Then you should be able to do what you want. 

I don't think that is going to work very well. You would be better off creating a new Cloud Jira Software site. You can get one for Free for up to 10 users. 

Hi Osama, Can you also post a screen shot of your rule? Is the rule firing? If so can you share the audit log of the rule when it fires? 

Hi Usmaan, You will need to create a new custom field of Paragraph type and put a Default value in the field. Then make the field Required in the Field Configuration. Put the field on the Create screen but not the Edit screen. Leave the Description field off of the Create screen but add it to the Edit screen. Then you can…

Have you tried a different browser? Or Incognito mode? If so and the result is the same, then I would submit a support ticket to Atlassian to see if they can tell what is going on. https://support.atlassian.com/contact/#/ Please post back here with the resolution. 

You will need to go to Settings > User Management > Products to see that. 

Ah yes - sorry forgot about that. You will need to add it as a Field Required Validator in your workflow. You can do that on the Create transition for when the issue is created if you like. 

That's the second time I have heard that in the past 24 hours. Assuming that the Statuses are in different columns, I would suggest submitting a support ticket to Atlassian to find out what is going on. If they are in the same column, you need to separate them to different columns to be able to drag and drop. Please post…

Hi Stoyan - Welcome to the Atlassian Community! The Jira Work Management product is still a relatively new product. And the Team-managed version of it is even newer. There will still be lots of fixes/enhancements/changes still to come. Personally, I do not like Team-managed projects and never use them. They are way too…

Hi Mike - Welcome to the Atlassian Community! Are the Epics on the same project? Or different projects? What type of project(s) is it? Team-managed? Company-managed? Is it JWM or JSW project? 

Hi Antoni - Welcome to the Atlassian Community! First, the Epic Link is a key value and not a name. So the Epic Link would never equal the Epic Name. Second, the Epic Link field is going away. You should use the parent field. Please share a screenshot of your rule so that we can help you better (after making the changes…

Hi Sakina, What type of project is it? Team-managed? Company-managed? Is is JWM or JSM project? Are you able to change the status directly on the card to the status you want? But just can't move it on the board? 

Hi Saurabh, What is the work type? Is that a custom field? So you don't want to get Epics, but you want issues that have certain values in a certain field in the Epic (I assume parent)? And what are you going to do with the results? 

Hi Miguel - Welcome to the Atlassian Community! What exactly are you trying to do with those? If software development, you should be using Jira Software, not JSM.