Kelly Arrey Expert

Hi @Jeanne ROBERT Sorry, I don't think it's possible for Worklogs to display the time by user within the task, you would need to run a Worklogs report or view a Worklogs gadget on a dashboard.

Hi @Ravi Kanth Sorry, I don't know any way of restricting the creation of a version name. Hopefully some more expert members of the community can chime in.

As Tom and Nic suggest, you should check for conditions on the Submit transition in the workflow. As an aside, it looks to me like there are two different things called "Submit" here, which are not necessarily related: * The Submit transition in the workflow that goes from Open status to Investigation status * A field…

Great minds @John Funk :-) 

Hi @Alex Larini A wild guess, but have you checked the "Allow rule trigger" box in the rule to create the issue? 

Hi @Low Darren, @Walter Buggenhout has pointed out one of the problems with the Team implementation. We implemented a custom select list (single choice) field we call "Agile Team" long before Atlassian introduced the "Team" field. We can can use the team names in JQL. We've also defined Jira groups with names that match…

Hi @Jeanne ROBERT, We've been very successful using the Worklogs by SolDevelo add-on to generate reports of time spent by team/person/month, etc. I'm not affiliated with SolDevelo, just a happy customer.

(As an aside, this question is tagged incorrectly - if you're on Jira Software (Server) 7.9.1, then this is definitely not a `cloud` / `jira-software-cloud` issue.)

“Ready for Development” sounds like a status. Can you write an automation rule to transition the issue to “Ready for Development” when those conditions are met?

@Valerie Capasso Glad you figured it out. I got bit by that a few days ago. For those following along at home, this is because Jira understands mm as minutes and MM as month, e.g., `dd.MM.yyyy HH:mm' 

I would try creating an automation rule using the "version created" trigger and then an "advanced compare condition" to compare {{version.name}} to a regular expression and send an email or slack message if it doesn't meet the naming convention.

Hi @Nikhil Kabadi I'm on Jira Cloud, and we're using company-managed projects. In my experience there are three things in the Project Settings that you should probably check: * The Fields tab - check the field configuration for the affected issue type(s) - if Fix versions is hidden, click on Show * The Screens tab - check…

Hi @Manoj Gupta MNNVL-6 is being pulled in twice, once under MNNVL-4, and once at the "root" level of your structure, which means that it meets the criteria of both your Insert Generator, and one of your Extend Generators. (As an aside, I can't think of any reason you'd need two identical Extend Generators for Advanced…

Hi @jun lee, I recommend that you investigate Structure by Tempo as a good way to visualize your issue hierarchy. I did a webinar on the topic in case it helps. They also have a Gantt Chart add-on that works with the Structure add-on. (I'm not affiliated with Structure, I'm just a happy customer!).

@Marina Kotler Hi Marina, what is your insert generator? 

You can, however, change the description of the field in the field configuration for that issue type/project, in case that's helpful.

Another approach might be to use Jira Automation to set a flag in the labels field, and then check that flag in the workflow transition.

Hi @Ashkhen Avetisyan, @Clark Everson's advice is very good. Also, I did a webinar on setting up a hierarchy in Structure in case this helps. We use a custom issue link type we call "contains <-> belongs to" instead of Parent links, because we like the flexibility of being able to skip a layer of the hierarchy, or for…

You could specify ISO 8601 format, i.e., yyyy-MM-dd :-) 

Glad you were able to figure it out! Thanks for the update, I'm sure this will be helpful to others.

Hi @Karoline Rezende Ramos Just a wild guess, but have you checked the `jira-issue-editable` property on the Closed status in the workflow? Here's a Jira KB article about it. HTH, Kel

Hi @Iavor Zayn Is it a custom field called Team, or is it the Jira built-in Team field? If it's the Jira built-in Team field, we ran into a problem with this situation because apparently Jira doesn't allow you to assign Team values to sub-issues - Jira "knows" that all sub-issues belong to the Team assigned to the parent.…

I'm very late to the party but in case anyone else wanders down this rabbit hole, I found this article: https://confluence.atlassian.com/jirakb/change-context-for-an-existing-custom-field-without-losing-old-data-674990056.html

What I'm suggesting is that you could add a transition from the current status to the current status, and make that the only way to edit the field you're interested in.

Hi @Sarit Ashtar One hack you could try if you're really desperate is to make this field editable only via a workflow transition, and then add a validator to the transition to make the other field required. Let me know if you're interested and I can outline the steps I would try. Kel

Hi @Dave in the interests of trying to understand the situation better so we can help: * What's the problem you're trying to solve? * Why do you want to link all the Bugs under a single Task? * What are you going to do with the Bugs once they're under this Task? * What are you going to do with the Task after all the Bugs…

Hi @Dave, Task and Bug are at the same level in the default Jira Issue hierarchy, e.g. * Epic* Story, Bug, Task* Sub-task One approach is to create a custom link type for this - we call ours "contains <-> belongs to", e.g., (We chose those names so that the few upward "belongs to" links would show above the many downward…

Hi @Dave, Please see my post below ... or above ... somewhere :-) , hope it helps. Kel

Thanks @Lynne Ratcliffe through your link I found Jira Cloud for Excel !

Hi @Rocsana Chereches I've attached a couple of screenshots to show where to find the issue history. If you have a wide browser window, you'll see several tabs at the bottom of the center pane, including All, Comments, History, Work log, etc., as shown in the first screenshot. In a narrower window, these will be collapsed…