John Funk Community Champion

How Gregory - You can't really change how the board operates in a Jira Work Management project. The ticket will always go to the bottom of the column on Create. 

Even better answer below! ;-)

Hi Eric, You should use a specific and unique Issue Link Type for the linking of issues between the JSW and JSM projects. Even create a new type if you want to ensure there is no overlap with other issues. Then base the trigger on the condition of having that specific link type. 

Hi Madelaine - Welcome to the Atlassian Community! Can you describe exactly what is happening in a little more detail?

Glad it is working for you!

Thanks, Mate!!

Hi @Devtech83 No, this is currently not possible. You should vote for and follow this feature request: https://jira.atlassian.com/browse/JRASERVER-16683

'Then you just need to change the Condition for the check on the stories. Make sure you use the Some match specific JQL option. 

Good - you have more flexibility that way. But I should have read closer the first time. No, issues on a Kanban board can only appear in one swimlane of a board. 

Hi Simon, No automation for Jira can't do that. ScriptRunner Behaviours is the only app I know that can do that. 

Hi Dominic, no, it is not possible to change the ID of the custom field. But you can change the name very easily.

Hi Season, This is a bug in Jira. You will need to edit the Field Configuration for the project and put in the new description for the field there. 

It is not matching the Condition where you are checking that the Stories in the Epic are in the To Do status. That is why it is failing. It's making sure that ALL stories are in the In Progress status. Is that your intent? 

とても良い - 明確にしていただきありがとうございます。 Paragraph タイプの新しいカスタム フィールドを作成します。 次に、フィールド構成に移動し、レンダラーを Wiki スタイルに変更します。 次に、カスタム フィールドの [コンテキストとデフォルト値] オプションに移動し、テーブルをデフォルト値に貼り付けます。

Loving your custom field name @Darryl Lee :-)

Hi Jason, Yes, because the label field is not a true text field. It’s more like a select. So you will need to use wild cards.

Hi Andrew, not that I’m aware of. That you can easily do a search and replace once you open it in excel.

Thanks for the invite - I have returned the favor 🙂

Thanks for sharing @Annie Lieu !!

Alright, let's take this in steps. First, remove the Story Points field from any screen that project is using - most importantly the Create screen if it is there. The transition screen is not the problem. Next, can you share the rule that you have create so far? Finally, I am still not following your flow. Are the check…

Hi Alicia - Welcome to the Atlassian Community! I think you have the < reversed. This could get everything that was updated more than 5 days ago. It's probably overwhelmed with the number of issues it is returning. Also, you don't want to use the Updated function but something like this: Status = DONE and status changed to…

HI Mark - Welcome to the Atlassian Community! Are you using a Team-managed Project or a Company-managed Project? 

No, that is a built-in system field. You can't function without that field in the system. Can you include a screenshot? 

Hi Onur, Edit your workflow and select the transition to the status you want to control (i.e. click on the line). Then click on Conditions in the right side. Then click on Add Condition and Select Value field. There you can select Issue Type for the field and then the value that you want to allow. See screenshot below. You…

Well, let's see if we can't make you a hero then my friend, because Jira can do all of that itself. :-) First, let's talk about the toolset and what they are designed to do. Jira Service Management is for help desk type teams and receiving intake requests, etc. Pretty much what you have in place now. And Jira Software is…

Glad to hear!

Hi Jisoo - Welcome to the Atlassian Community! Permissions to individual projects are controlled by the Permission Scheme for the project. Just because a user has Jira product access doesn't mean they can access any and all projects. Check the permission scheme for who has Browse Project permissions and add the users. By…

Hi Arnold, Why not add a Validator to the transition in the Dev team project workflow to require the field be populated before moving it to ready for test? 

Hi Fuadilah - Welcome to the Atlassian Community! It depends on your workflow for the Epic issue type. What status are you moving from and to which status are you going? Are their Conditions or Validators on the transition to that status that might be preventing the transition? 

Sorry, I also just noticed that it is a Jira Service Management project. Currently, there are issues with creating a sub-task on those projects. You can vote for and follow the feature request here: https://jira.atlassian.com/browse/JSDCLOUD-1422 So, then comes the next question - why are you trying to create Sub-tasks on…