Walter Buggenhout Community Champion

Hi @Dennis Celen and welcome to the Community! It is great to see that shortly after you started using Jira you're also starting to ask yourself questions. Not only about how the tool works, but how it may best support how your company or organisation is trying to do its work. The tool(s) should support your organisation…

Hi @Ndane Elisha mankaa and welcome to the Community! Jira Software is built with agile projects in mind. It is a great idea and the perfect mindset to start from the idea that you don't want to just learn a tool, but see the bigger picture where the tool helps you run better projects! A great resource to get you started…

Hi @Dennis Celen, First of all check if you're in a team managed or a company managed project. It shows in the left bottom corner of your screen. If your project is team managed, there should be a ... button near the top right of your board. Select Configure Board to display settings: If your project is company managed,…

Signed up @Christina Ristevski. would be really great to check out in the context of remote workshops at first glance. 

Hi @Andrew.Heawood and welcome to the Community! The advanced roadmaps teams you refer to are referenced with a number rather than the team name. And so, in order to make your quick filters work, you should use the numeric value that represents the team instead of its name. It is indeed not quite easy to retrieve what…

Hi @[deleted], There's nothing wrong with the history there. The values that are entered when the issue is created originally are not listed. The description, summary, reporter and other fields that are there are also not listed. When the history says the assignee was changed, that just means that an update of the field…

Hi @Phil Noble and welcome to the Community! It is exactly as you explain: there has been a program view in an old version of Advanced Roadmaps Server, probably even in the days when the product was called Portfolio for Jira. That view has never been updated with the new way plans work and it has never been made available…

Hi @Evalaji Jones, An issue in Jira can only have one assignee at a given point in time. You can change the assignee of an issue to someone else, who then becomes the owner of the issue. But you can't have multiple assignees. A common workaround to involve multiple people on a issue, is to add an additional user custom…

Hi @Pierangelo Repetti, No, it does not. If you assign a permission through a permission scheme, you only assign what is meant by that permission. e.g. Administer Project does not even grant the permission to view the issues in the project (that's what Browse Project does), or the ability to edit or assign issues. You'll…

Hi @Sreenadh, Automation rules are meant to make things happen, rather than preventing them to happen. However, if you are using company managed projects, you can add a condition to a transition that is blocked by the status of your sub-tasks: Edit your workflow, select the conditions for the transition you want to…

Awesome! Great to hear! If you could accept my answer, it also makes it easier to find for users with a similar need; thx and happy planning / tracking!

You are right that you cannot do these two things in one single action. But nothing is stopping you from adding 2 edit issue actions to your automation rule: one to copy the components and an extra one to add the new component.

Hi @Andreas Lärkfeldt, yes it does. Simply click on the ... button right next to the field and select COPY instead of SET. Then you are able to select the source issue you want to copy from:

Hi @Jeannette Bakken, JQL retrieves issues and not worklogs. And for you filter to return results, the information you use to fetch those issues should be explicitly on them. I suspect that Team.Program is not filled out in a field on your issues and that's why the query does not return anything. So if you want to build a…

Hi @Elif Alverson, The most important thing you should do, is first of all make sure to get the data from your custom field copied over to the system field. You should be able to pull this off with an automation rule. As a trigger, choose scheduled and add a JQL statement to retrieve the issues that have a due date filled…

Hi @JayJuan Jones, A regex validator on the create transition of your workflow is basically the out-of-the-box way you could set this up. This KB article has a good description of your use case. It even refers to a phone number custom field as an example on how to set it up. Hope this helps! 

Hi @Cash Coyne, JQL does not do that. It is a query language that lets you retrieve a list of issues. The scenario you describe is something that you would probably want to do if you intend to perform some actions with the issue(s) you find. And if that's what you are looking for, Automation rules give you the possibility…

Hi @Jenny Mattson, No. People still need a license to use your Atlassian products, no matter if they are part of your organisation or not. Access is a subscription that centralises user management across all your Atlassian Applications and that lets you integrate with an Identity Provider, so you can also set up SAML SSO.…

@Ivan Andrieiev, You are basically saying that you want to create a recurring task that needs to be generated every single day. That was not really clear from your initial question, but if that's what you need, a scheduled solution as offered by @Ste Wright here should be able to deliver what you need. 

Yes, I kinda felt that one coming 😉 Sprint in OpenSprints() and resolution = unresolved That would retrieve all open sprints across all boards in Jira. So if you want to refine further, you may want to add an additional restriction on the projects you want to include in your search: Project in (ProjectA, ProjectB,…

Hi @[deleted] and welcome to the Community! Assuming that your roadmap is in a Company Managed project, navigate to Board Settings from the board view in your project. Navigate to the Roadmap page in settings and set the toggle for child level issue scheduling to on: After that, you should be able to add roadmap bars to…

Hi @Evalaji Jones, The following should do the trick: Sprint = <your sprint> AND resolution = unresolved Hope this helps!

Hi @Ivan Andrieiev, Create an automation rule with a manual trigger. As automation action, select clone issue and define the fields you want to copy. You should be able to trigger that rule from an issue, by selecting the Automation rules link in the details panel of an issue you open. Hope this helps! 

Hi @Ahmed Safwat Marey and welcome to the Community! You need to first configure your SLA targets and corresponding calendar so it starts and stops the timer during weekdays only. See product documentation on SLA configuration for all the details. Once you have this properly set up, from the left hand side navigation in…

Hi @rohit bhatia, If you look closely at the status Finalised by client you'll see it is green. That is in Jira a Done status and I suspect that issues that reach that status are probably also getting a value set in the resolution field. As of that moment, Jira considers these issues as done. When an issue is done, it is…

Hi @Darren Simons and welcome to the Community! The link you click in the backlog view is designed for quick, in-line creation of issues with limited fields just to be able to move fast. If you want to add the full details of an issue, you can always do so (wherever you are in Jira) by clicking the big create button in the…

Hi @Bayar Said, Have you considered adding Confluence to your site? It gives you all the capabilities you ask for and much more and integrates seamlessly with Jira. 

Hi @Melissa Clark, It is all in all not that difficult, but there's several different configuration options due to the different project types indeed. Company-managed projects Jira has a fine-grained permission system with a lot of detailed permissions. All these (available) permissions are grouped in what we call…

Hi @therjmb, You are basically right that you need to have all your tasks in one board if you want to put them in a single sprint. This is simply because a sprint is a feature of a scrum board (company managed) or a specific feature that you can enable in the feature set of a team managed project. You do not need to put…

Hi @Sam Kang and welcome to the Community! Two possible reasons come to my mind: * either there is a post function in the workflow associated to this type of issues that sets the assignee automatically. Assuming that you are in a company managed project, you can check this via project settings > workflows and check…