Walter Buggenhout Community Champion

Hi @Naomi Carey and welcome to the Community! On the create transition of your workflow, add a Field Required Validator. It will make sure that the user has to enter a value for this field before he/she can create the issue. Hope this helps!

Most likely this stream field has been set as required in the field configuration linked to your (company managed) projects. Open project settings of any impacted project, navigate to project settings and have a look what field configuration it is using. A Jira administrator should be able to verify the settings for this…

Hi @Samuel Westen and welcome to the Community! I am not sure what your actual question is here. Indeed, as the screenshot says - you need access to the ticket in the other Jira instance in order to be able to preview the issue in this instance. The message refers to Jira's smart links, where you have the possibility to…

Hi @Alex Borges da Silva, Check your Jira settings / global permissions - in order to see users in a user custom field your users must have browse user permission. Hope this helps! 

Hi @[deleted], If this is a recurring process, you may want to look into syncing apps. This marketplace search may be a good starting point for you to compare your requirements against the feature set offered at what cost. Hope this helps! 

Hi @Trena Norcia, Assuming you are using a kanban board in company managed project - the issues on the board are selected from the board filter, which you can retrieve and edit from your Board Settings > General > Saved Filter If you want to see both your epics and tasks, you must ensure that the tasks linked to your epics…

Hi @venkatesh bojja and welcome to the Community! It seems like it would not be a bad idea to read some of the Advanced Roadmaps documentation. In short, you'll need to define the issue hierarchy in Jira to define how issue types relate to one another as parents and children. Next, when creating a new plan, you will have…

Hi @DiegoMX, If you are trying to automate a team managed project, you may be running into a known limitation that is described in this support article. There is a feature request for this that you can track here: AUT-919 Hope this helps! 

Hi @Meenakshi G, There may be quite a few reasons for this: * The issue types you create centrally in Jira are only available to company managed projects. If you were trying to use them in team managed projects, that won't work by design. * When working with company-managed projects, you must not only create the new issue…

Hi @Nellie Ochs and welcome to the Community! Are you sure your project is a Jira Software project? The tags and the title on your question suggest that you are using a Work Management project and - if so - the group by options there are different indeed. As a comparison: Jira Software / Team managed Jira Work Management /…

Hi @Javid Huseynli, One thing that is tricky is that your board filter is too generic. Because of the red rectangles on the screenshot, I am not entirely sure of what is there, but if that is an "OR", you are potentially pulling in issues from every single project in your Jira instance, including team managed projects. It…

Hi @[deleted] and welcome to the Community! Resolution is not a status; it is a field that should be filled out when you move an issue to a done status. Also, and maybe more importantly, issues in a kanban board are considered done when they reach the rightmost column on your board. Regardless of status, that setting will…

Hi @Vishnu Vardhan Chenna, Assuming that the project you are trying to automate is company managed, can you make sure that Project Role (atlassian-addons-project-access) has all necessary permissions in the permission scheme used for your project? That would at least be browse project, edit issues, transition issues. Also,…

Hi @Andrés Denis and welcome to the Community! Jira does not work the way you are trying to implement it. Your estimations (in Orgininal Estimate) should be at the Story level. These are the items your team delivers (as a whole), and while sub-tasks can be added to split the work into smaller pieces of work to be worked on…

 Hi @usman_malik, Advanced Roadmaps has a feature set allows you to: * extend the Jira hierarchy above Jira's standard level of epics; * build a visual roadmap across multiple data sources; * group releases coming from multiple sources into cross-project releases; * use the built-in warnings center to be alerted when your…

Hi @Danilo Simic, The short answer is no. The items displayed for linked issues are not configurable. There is a suggestion in the backlog to allow configuration of the panel that you can track here: JRACLOUD-36490. You'll notice several linked issues however that have been closed as won't fix. Hope this clarifies!

Hi @Riley Sullivan, I think the key element to understand the complexity, is that releases in Jira are linked to a (Jira) project. As your screenshots clearly illustrate, even if your releases have exactly the same name, they still are different artefacts in Jira. It has been (and still is) common practice to set up a Jira…

Hi @eric_mcdougall and welcome to the Community! It seems from your first screenshot that you have renamed two of your Jira issue types. In advanced roadmaps, these issue types are mapped to levels in your hierarchy structure which have their own naming. That allows you to map multiple issue types to the same level in the…

Hi @Jonathan Waite and welcome to the Community! Every transition in Jira has 5 post functions configured by default. The last one is the one that fires the event: You can edit that line to throw a different event, but you can not add an additional event. Hope this helps!

Hi @Danielle Koby, No, that is not possible. Although JQL is quite powerful, it lacks certain capabilities a database query language has (such as combining multiple data sources using JOINS, like in SQL). You can only work with the data that are present on the issues retrieved by the search for stuff like e.g. sorting.…

Hi @Levine and welcome to the Community! There is something strange about your use case. From what you describe, it seems you want to track the number of story points completed. But that seems something you would do when a story is actually completed, rather than after you update a story point estimate. If I understand…

Hi @Phil Bustin, It depends if your workflow is in a team managed or company managed project. For team managed projects, this is currently only a feature request that you can track here: JSWCLOUD-21700 For company managed projects, yes you can! Workflows are managed centrally by a Jira administrator under Jira settings >…

Hey @Sara Bernate Angulo, From your follow-up question, I assume you are using team-managed projects. I am afraid I'd have to disappoint you there - there is a feature request for that customisation that you can track here: JSWCLOUD-17336 (you can add a cover image to your cards to cheer them up, though) As mentioned in…

Hi @Sara Bernate Angulo and welcome to the Community! No, customisation options do not go that far. You can add up to 3 custom fields to a card on the board, but you do not have much control about their placement on the card. Hope this clarifies!

A test site is free for 30 days. You can set up as many as you need, on the plan you want. But you should not set up SSO to that test site. You use it to validate the technical migration aspects. From your questions, I get the impression that you have not reached out to Atlassian Migration Support. Definitely do so,…

And to mine as well 😀 - thx for the heads up!

Hi @Petter Topp and welcome to the Community! That is not how it works, unfortunately. You do not only migrate data, but also configuration, users, attachments and so on. The idea is you migrate a project with its issues once in production and then you switch over to the migrated environment. You can choose to migrate a…

Just trial and error to be honest, but maybe that's because the function should be inside the math tags at the beginning and end. {{#=}} ROUND({{issue.customfield_10679.asnumber.plus(issue.customfield_10680.asnumber.plus(issue.customfield_10681.asnumber))}} / 3, 0) {{/}} If that doesn't work, you may want to look at @Bill…

Hi @Genevieve_Green, I don't have a working environment where I can test, but given the complexity of your formula I suspect the best way to try and achieve what you're after may be through a ROUND() function. Something like this: ROUND(…

Hi @Anita Domańska, The case you describe is difficult to assess without insight into the details of your configuration. But (assuming your projects are company-managed) screens are associated with projects through a set of screen schemes; Trying to avoid over-complicating, you can basically perform 3 different operations…