John Funk Community Champion

Hi Jill, Yes, you can create Company-managed projects for Jira Work Management. They were actually the first type and then Team-managed was added later. Unfortunately, they have made Team-managed the default type, so if you are not careful, you will not see to change that. Be sure to click on the Show More link on the…

Hi Luan - Welcome to the Atlassian Community! You can use some smart values/code, but it depends on the type of fields being used. Can you provide more information for the types of fields you want to include? 

No, I think you will need to contact Atlassian support unfortunately.

Great!

Hi Phil - Welcome to the Atlassian Community! No, you cannot duplicate a board for JWM projects. But you can create a Jira Software board and use it in addition to the JWM built-in board. Here is an article that describes how to do that.…

Yeah, to me adding a comment should constitute an update as well. But glad that worked for you!

I suspect the automation rule is triggering on something else and not the Updated date itself then. But I can't answer that or tell you what constitutes an issue being "updated". I can just a solution based on the observances you describe. 

It sounds like you are either using different mail handlers for each or there is something different about how the mail handler is processing them. 

Hi Adithya - Welcome to the Atlassian Community! Are you using Jira Service Management and the built-in approval functions that come with that product? 

So, that tells me that adding a comment to an issue does amount to "updating" it in Jira's eyes. You would need a second rule that handles those - you should be able to simply copy your existing rule and change the Trigger to Comment added instead of Issue Updated. 

Like @Jimmy SeddonI got to see this one recorded live, and what a neat experience to see that happen. Teams should definitely have outings and enjoy time together when you can. But I am not sure that forcing that to happen for virtual teams is the right way to go. Maybe in small doses it might be okay, but most of us don't…

Hi Gavin, What did you change that should have updated the issue? And what that change done directly to the issue? Or was it a change to the issue as the result of another rule running that updated the issue? 

Hi Peter, I am not aware of a way to do that, except manually. Out of curiosity, what type of field is it? 

Hi Willi Set the value of a custom field when you run the rule - any field type and any value. But then add a check of that field with a condition at the beginning of your rule to make sure that field does not have the value (or is Empty). 

Yep, that worked - thanks @Mikael Sandberg !

Hi M, Make sure this is an actual transition from that status to another status. Then check to see if there are any Conditions on the transition(s) out of that status. 

Hi Rohit, You are using two different project types - the top one is a Jira Work Management project and the bottom one is a Jira Software project. JWM projects have a built-in board that cannot be configured like the Software board can. However, you can create a second board for JWM projects that you can configure. Take a…

Hi Shane - What type of project is this? Company-managed or Team-managed? 

Hi Lana - Welcome to the Atlassian Community! You might be able to do it through the API - but that's beyond me. You could probably have your spreadsheet completed by the time you figure what whether the API can do it or not. :-) 

No idea - that's just how they set it up. But why would you allow some users to change sprints that don't have permission to rank issues? 

@Ali Aydın - Did your automation rule fire? And if so, what did the Audit Log say?

Hi Kiranmai, If you have sub-tasks as children then, no you will not be able to have separate issue security levels as the child sub-task inherits the level from the parent. Other parent/child relationships you could do separate levels with though - like with Epics and the children of epics. 

Hi Swaroop, No, there is no dependency there - you just get both right now. There are no separate licenses right now. A year from now there will be a separate subscription for Jira Work Management apart from Jira Software. You still handle access to any of your projects based on the Permission Scheme for the project. 

That's the only thing that is available - you won't be able to selective give permissions for ranking apart from that. 

Hi @Roee Fogel - Welcome to the Atlassian Community! The permission to rank issues is based on the Schedule Issue permission in the permission scheme. So, just change the scheme to limit who has that permission. 

Hi Jennylee - Welcome to the Atlassian Community! Are you positive that the To: address is exactly the same in both cases? 

If you create a Proforma form, you should be able to add what you like. 

Hi @Ndane Elisha mankaa - I don't really have a group. :-) I just answer questions that I can. I believe there is a new version of Community coming out soon though that will let you follow a user. You could follow me at that point if you like. I would encourage you to subscribe to the notifications for the questions for…

HI @Murat Memioğlu Did you ever get this solved? I suspect there is a problem with the permissions in the Permission Scheme itself. 

Can you share the screen print from the audit log like to did above for the Monthly A and Monthly B fields where you logged them?