John Funk Community Champion

Hi Ox, Are you using the built-in form that comes with the Request Type? Or did you create a separate form using the Proforma form that now comes with JSM? 

Hi Kerri, So, just to recap - you see sub-tasks on the board at the same time you see other issue types. But if you use the Assigned to Me quick filter, it shows some issues assigned to you, but not the sub-tasks associated to you, if the Sub-tasks assigned to you have a different person assigned to the parent. Is that the…

Hi @Ansu Achu - Did you complete the move? Can you share any tips or helpful things to remember that you encountered?

Hi Romain - Welcome to the Atlassian Community! When you do the move, you should be able to designate which status the current issues are moving to. So, I would do bulk change moves based on only moving the issues in a particular status. Do that multiple times for each set of issues for each status that current has issues…

Well, I would contact Atlassian Support to see why they created that issue. 

Is that the exact name of the user? 

Great! Glad that worked for you. 

This is very timely with the ever growing interest in Dev Ops. Should be some good reads!

Hi Hila, If a new issue in JWM is being created, then it is because someone has added an automation rule (or a post function in the workflow) to create the issue. You just need to turn that off. Check the history of the JWM issue that is created to see who it says created the issue. 

Hi @Christopher - Did you ever get this sorted out? Can you provide what you ended up doing? 

Hi Alexandra, I have been seeing a lot of problems with this field and the smart value recently. Maybe try using the customfield id for it. {{issue.customfield_10156}} where 10156 is the ID of your Start date field. You can find that by searching for the field - go to Settings > Issues > Custom fields search for Start…

Just that the process was completed when you click on Create project

Hi Keith, I am not real sure what will happen with this since it is also the step with the approval. I would assume it will fail if someone approves the issue and the Planned start is in the past, but how will the user know that because there are no messages that go with a Condition - just a Validator.

Hi Valentino - Welcome to the Atlassian Community! Only issues in the far right column will be considered Complete for Sprints. You will need to move both of those statuses to the last column.

Like Peter I prefer to go to different places each time usually. However my oldest son lives close to Glacier National Park - so beautiful!!

What do you mean by it’s still showing the same? Did you grant that user create issue permission? If so, edit the permissions scheme and take them out

You can’t make someone a Jira Admin if you are not one yourself.

Hi @evenings session - Welcome to the Atlassian Community! Go to the Permission Scheme for the project - make sure it is definitely the one used by the project and what you “think “ it is. Then use the Permission Helper for that username and the Create Issue permission to see what it says.

Great!

Create a rule with an Issue Created trigger Then add any Conditions you need to (if any) that will narrow down this type of issue to be transitioned automatically. Then add a new Action for Transition Issue and choose the Status that you want to transition to. 

There was probably another status that got created called In Progress. So in your workflow, you should be able to change out the HM/MH one and add the a new status and select In Progress. Just disconnect all of the transitions from the HM/MH status - you won't be able to delete it in an active workflow, but you can make it…

Not if your Start date was two days before your Due date. Which I would hope it is. :-)

JMWE is an excellent (maybe the best) app for me to create post functions. 

Atlassian's example uses {{issue.duedate. Try that format again with the now option and see if that works. And if so, try to string them together again. 

ah, it might be something related to how a variable handles values - meaning it might not be natively using it as a number. But that's beyond me. Maybe @Bill Sheboy can weigh in. 

I would contact the vendor and ask them the intent of the Append function and how to solve. 

Hi Christoph, You should be able to go to Settings > Issues > Statuses and find the HM/MN status there and change the name. 

I would think yes that you could do that. Try the Copy to New select the Summary from the source field to Summary field of the destination and use Append. Give that a try and see how it does. 

Do what you have done above, but Log the Monthly A and Monthly B fields, etc. 

My apologies for not being clearer. I meant try this: {{now.diff(issue.Start date).days}} and see if it populates anything. Or {{now.diff(issue.Due date).days}}