youngmon/atlassian-qna huggingface dataset:
Admin is unable to switch workflow inside active behaviour
Asked by Gilad Shtern:

Hi,

I create a new workflow in which I'd like to switch in an active behaviour.

However, I failed to do so.

We're using Data center 8.22 with ScriptRunner 6.57

Kindly, Gilad


Answers:
author: Lisa Forstberg
body: Hi [@Gilad Shtern](/t5/user/viewprofilepage/user-id/4258602)

What happens when you try to publish the workflow? What error message appears?

It is always good to add screenshots and the steps you performed so we can give you the support you need :-)

A common problem is that admin forget to actually click the publish button after adding the workflow to the workflow scheme. Go back to your project \> project admin \> Workflows just to check of the blue publish button is there or not.

All the best

L

comments: author: Gilad Shtern
body: Hi [@Lisa Forstberg](/t5/user/viewprofilepage/user-id/5101516)

The workflow is OK. however when I try to switch inside the Behaviour I can't find it \& get followed error:

"There was a problem fetching the workflow perhaps it was deleted."

So, how it can be deleted when users are really using this WF?

Kindly,

Gilad


author: Lisa Forstberg
body: Hi!

Oh I see, the error appears when you're working in Scriptrunner \> Behaviours. I think you are better off contacting the Scriptrunner support to get speedy help. They have always been really good and helpful to me anyways :-)

best of luck

/L


Tags: data-center

jira-data-center
Block transition of a task based on the status of a task in another project
Asked by Michael Maram:

I want to block transition of a task to 'In Test' unless all of the linked dependent tasks in a different repo have a particular status.


Answers:
author: Maciej Dudziak _Forgappify_
body: Hi [@Michael Maram](/t5/user/viewprofilepage/user-id/1609085)

If you are open to using apps and looking for a ready-to-use solution. We've developed the Linked Issues Validator available as part of the [Workflow Building Blocks for Jira](https://marketplace.atlassian.com/apps/1233642/workflow-building-blocks-for-jira?hosting=cloud&tab=overview) app. With a wizard-like UI, you can choose relations from: sub-tasks, parent issues, epic children, and linked issues. Additionally, you can filter relations by issue types and select criteria based on status category and status.

I hope it will help.

Cheers


author: Hans Polder
body: [@Michael Maram](/t5/user/viewprofilepage/user-id/1609085) ,

You could solve this in numerous ways.

1. There will likely be plenty of apps in the Marketplace (that might be paid for) that would allow you to do this out of the box. If you want a neat solution that can be re-used and applied in different parts of your system (in multiple workflows), you might want to check that out.
2. Native Jira doesn't support a condition on a transition that checks for 'linked dependent tasks'. However, what you could do is a variation of the 'potential solution' I've described below.

**Quick \& dirty solution**

1. Create a custom field but don't make it visible on the Edit Screen, but not View or Create Screen of the issue type you're working on.

2. Use Jira Automation (a global rule that can only be managed by admins) to trigger on 'Task closed \> check parent \> for parent, check if all linked childs/tickets are matching a certain JQL (as in "all are closed") \> then fill a certain value in the created custom field.

3. THen, in the workflow for the ticket that must not go to 'In Test' if the linked tickets are not closed, you can add a condition for 'Value Field', referring to the custom field that you are updating via Automation to be a certain value. If that value is met, then the condition will allow the transition to be visible.

It's not pretty, but it should work. Again, if you need to do this more often, definitely consider Marketplace apps for this :)

comments: author: Michael Maram
body: Thanks [@Hans Polder](/t5/user/viewprofilepage/user-id/5506451) - I am trying to stay away from a paid marketplace option which can be quite expensive. I will look at your alternate solution.


author: Hans Polder
body: Let me know if it works out! :)


Tags: cloud

jira-cloud
Is it possible to make a linked issue the parent of the original issue via automation?
Asked by d_kamposos:

Hello all,

I have 2 issue types, 'Eng.Problem' and 'Change Request' (CR). Their issues are connected with a custom link 'solves - is solved by', where a problem is solved by one or more CRs and a CR solves exactly 1 problem.

This worked fine, until we decided that we want a parent-child relationship between them. So I 'upgraded' Eng.Problem to level 2 hierarchy and CR to level 1, so now a CR can be the child of a problem.

The final step is to take the linked problem from every CR and assign it to the parent field. I tried to do it with an automation but I keep getting the same error (data was not an object(parent)).

![crs.png](https://community.atlassian.com/t5/image/serverpage/image-id/339375i4D756453D9D3BD32/image-size/large?v=v2&px=999 "crs.png")


Answers:
author: Sebastian Krzewi?ski
body: Hi [@d_kamposos](/t5/user/viewprofilepage/user-id/5436212)

I think you are using wrong json to set parent. Please check this thread - <https://community.atlassian.com/t5/Jira-questions/how-to-update-the-parent-field-of-an-issue-with-API/qaq-p/2574491>

Regards,

Seba

comments: author: d_kamposos
body: Thank you [@Sebastian Krzewi?ski](/t5/user/viewprofilepage/user-id/1561725) , that's what I needed!


author: Bill Sheboy
body: Hi [@d_kamposos](/t5/user/viewprofilepage/user-id/5436212)

Please post an image of the audit log details showing the rule execution. That may help provide more context for this symptom. Thanks!

Until we see that...

You could restructure your rule to only process when there are issues to update. For example...

* trigger: scheduled with JQL to find CR issues without a parent and which have your linktype
* action: edit the parent field directly, setting the value to the smart value expression for the linked Problem issue
* *Do you also want to remove the link after setting the parent? If so, continue the rule with...*
* action: re-fetch issue
* action: delete the issue link of the specific type

Kind regards,  
Bill

comments: author: d_kamposos
body: Hello [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313)   

My problem was the wrong JSON format that I used, so I accepted Sebastian's answer, but thank you for always being helpful and pointing out additional concerns!


Tags: automation

cloud

issue-link

jira-cloud

parent
task management allocation by using AI
Asked by Nik Meerwinck:

Im looking for ways to implement an AI that uses machine learning and data analysis to identify the best candidates for specific tasks, making the assignment more efficient and targeted. E.g. assigning tasks in Jira based on the prior data analysis


Answers:
author: Vronik
body: Hi

I think you'll still have to wait, but in the meantime take a look at these articles

<https://www.atlassian.com/software/jira/service-management/features/itsm/ai>

<https://www.atlassian.com/platform/artificial-intelligence>

<https://support.atlassian.com/organization-administration/docs/atlassian-intelligence-features-in-jira-software/>

<https://www.atlassian.com/trust/atlassian-intelligence>


Tags: ai

cloud

jira-cloud

not-applicable

organization-administration
How to show the custom field in the side pane of TLE and quick edit?
Asked by Christy Lim:

How to show the custom field in the side pane of TLE and quick edit?

For example: To allow the custom field "Branch" shown in the side pane of TLE similar to "Labels" , "Customer" are shown. So that the edit can be done more easily.


Answers:
author: Dave Mathijs
body: Hi [@Christy Lim](/t5/user/viewprofilepage/user-id/4501702) welcome to the Atlassian Community!

What do you mean by "TLE", what does that acronym stand for?

You might want to have a look at the **Issue layout** of a screen:

An issue layout has four sections.

**Description fields section**

Fields placed in the description section will show on the main area of the issue view. This section must always contain the Summary field, which cannot be removed or reordered.

**Context fields section**

Fields placed in the context section will show on the right side of the issue view in the Details panel. Most fields can be ordered as desired. This section will always contain the Status field, which cannot be removed or reordered.

**Hide When Empty**

A field placed in this section of the issue layout will show in one of two locations, depending on whether the field has a value.

If the field has a value, the field will be with the other Context fields within the Details panel.

If the field is empty, it will be in a collapsible section called "More fields" underneath the Context fields section. If a user wants to populate the empty field, they can expand the "More fields" section and edit this field. Upon browser refresh or upon returning to the issue, that field will then show in the Context section.

### Hidden fields {#toc-hId-2147358229}

With issue layout, project admins can also configure field visibility by placing fields in the Hidden fields section, so they are never displayed, regardless of whether or not they have a value.

You can find additional info in this documentation article: [**Configure issue layout**](https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-layout/)


Tags: cloud

jira-cloud
Earlier Start date and End date use be available for every story created, where I can find those now
Asked by Biswas,Barun:

Earlier Start date and End date use be available for every story created, where I can find those now


Answers:
author: Hans Polder
body: [@Biswas,Barun](/t5/user/viewprofilepage/user-id/5558166) ,

Welcome to the community!

Can you share a bit more context? Maybe a screenshot of where you used to see the fields, and now they are gone?

My first thought would be that someone edited some configuration causing the fields to be hidden or removed. Do you have admin permissions in your environment by any chance? Otherwise, it would be wise to contact your project admin or product admins to get it sorted.


Tags: cloud

jira-cloud
Unable to create Programs in Portfolio 2.6.0
Asked by Alessandro Placidi:

Hello,

I have updated Portfolio for JIRA to version 2.6.0 and, according to the release notes, Programs have been rolled out. Despite that, I can't seem to be able to create one.

I have read through the documentation and followed the instructions there, but I can't find the elements mentioned, like the new permissions or the Create Program option.

My UI is exactly as it was before the update and it only mentions plans. All other new features, like the dependency report, are there so I don't think the update to 2.6 wasn't successful.

Anyone had the same issue?


Answers:
author: Roi Fine
body: Hi Alessandro,

We released a fix for it on version 2.6.1

Please update for the new version to enjoy the full functionality of Programs.

I hope that helps,

Cheers!

comments: author: Alessandro Placidi
body: Hi Roi,

versione 2.6.1 fixed my issue completely.

Thanks!


author: somethingblue
body: Hi Alessandro,

I spoke to one of the Portfolio devs and they believe they found the issue. They took 2.6 off the Marketplace and they put up 2.6.1. See if that resolved the issue for you.

Cheers,

Branden


author: Eric Franklin
body: Hi Alessandro,

Just to be clear, when you go to \<instance_URL\>/secure/PortfolioPortfolioManage.jspa and click 'Create', you don't see the option to create a Program, is that correct? By default, if you are a Portfolio for JIRA user (you configure these permissions in \<instance_URL\>/secure/PortfolioPermissions.jspa), you should be able to Create a program, and once created, program permissions can be modified. Also, in case it helps, here is the document specific to program permissions:

<https://confluence.atlassian.com/jiraportfolioserver/configuring-program-permissions-934719069.html>

comments: author: Alessandro Placidi
body: Hi Eric,

thank you for your help! In fact, manually using your link I am able to access the page where I can create a program.

What is strange is that in my top bar Menu, inside Portfolio, I don't have any item that links to that URL. I have instead:

* The latest recent plans.
* View All Plans
* Manage Shared Team
* Create Plan
* Administration

It's as if I have all the functionality I need, but the menu in the top bar has not been updated to reflect them.


Tags: advanced-roadmaps
How to I upgrade to Jira Portfolio 2.5 on my server instance
Asked by Ian Rees:

I have Jira Portfolio 2.4 installed on a Digital Ocean droplet and I have seen emails saying 2.5 is available. I've searched around the various menu options but can't see how to upgrade. any help appreciated


Answers:
author: Walter Buggenhout
body: Hi [@Ian Rees](/t5/user/viewprofilepage/user-id/1144420)

Log in as Administrator in JIRA, navigate to the Admin section of your JIRA instance (not Portfolio), locate the 'Add-ons' section.

*the quickest way to do this is just type g+g and in the dialog that appears type 'Manage add-ons'. It will bring you there right away*.

In the list of your installed add-ons, locate 'Portfolio for JIRA' and click the blue update button:

![Screen Shot 2017-09-05 at 20.16.20.png](https://community.atlassian.com/t5/image/serverpage/image-id/5671i9836CED3CBD2EF79/image-dimensions/449x45?v=v2 "Screen Shot 2017-09-05 at 20.16.20.png")

An alternative would be to first download version 2.5 from the Atlassian Marketplace ([located here](https://marketplace.atlassian.com/plugins/com.radiantminds.roadmaps-jira/server/versionhistory)) and upload it through the same Manage add-ons page. The first option will be quicker, though.

comments: author: Ian Rees
body: Thanks.


Tags: advanced-roadmaps
Automatic Scheduling calculates a very inefficient plan
Asked by Anders Dehn:

I'm setting up my first plan, but it seems like the auto scheduling does not work.

One of the times I recalculated the plan and it looked right be next time it started to look wrong again.

Help me find the problem:

I have a story that will not be started today but is planned a week ahead and this is not right if I look at the cal rules behind.

1. it is the highest in priority

2. it has no blocking issues

3. the person assigned has no other issues

4. it is the critical largest issue in the plan

what have I done wrong?


Answers:
author: Mar?a
body: Hi Anders,  
You might find the following links useful to learn how to use Portfolio.

* [Creating your first plan](https://confluence.atlassian.com/jiraportfoliocloud/creating-your-first-plan-and-succeeding-828785200.html)
* [Getting started](https://confluence.atlassian.com/jiraportfoliocloud/getting-started-with-portfolio-for-jira-873926170.html)
* Learn more about [Portfolio scheduling and timeline](https://confluence.atlassian.com/jiraportfoliocloud/scheduling-and-timeline-828785384.html).
* [Sign up](https://confluence.atlassian.com/jiraportfoliocloud/webinars-937164847.html) for upcoming webinars and learn more!

Cheers,

comments: author: Anders Dehn
body: Hi Maria,

I have read all the documentation carfully, but do not find answers to this question.

We are considering investing in the tooling, but if this core functionality cannot work, it is probably not going to happen.

Any possibilities for getting support for this issue ?


Tags: advanced-roadmaps
Why won't a release show up in Portfolio
Asked by Jacob Peebles:

I have a release which will not display in portfolio. I have checked its settings against other releases and see no differences...it simply does not show up at all when I go to releases and search for it.

<br />

Any ideas? This is pretty frustrating as this release contains a number of epics which also do not show...I'm assuming because they are related to this invisible release.

Thanks,

Jake


Answers:
author: Walter Buggenhout
body: Are those Epics and Release part of the source data of your Portfolio Plan?

Have a look at your Plan settings:

* Plan / Configure (through the button with ... next to the Plan's name)
* Select **Issue Sources** from the options on the list
* Click the **Edit Sources** button

You will then be guided through the wizard that was initially shown when you first set up your plan. Check whether all your projects are included in the selection on Step 1. In step 2, you may include additional releases if they are there. Step 3 are your issues (so Epics too).

You should be able to locate everything there and fix issues with the data selection, if that's what is causing your issue.

comments: author: Jacob Peebles
body: Okay, so this appeared to be the potential issue, the Initiative in question was not selected. So...

- I selected it

- Tried to move to the next step, step 3 but got this error on page...

![Can't save settings.gif](https://community.atlassian.com/t5/image/serverpage/image-id/5577i44EBC02CC837C149/image-size/large?v=v2&px=999 "Can't save settings.gif")

Any ideas?

Thanks,

Jake


author: Walter Buggenhout
body: One thing you might check, is whether all issue types in the project selection are configured in Portfolio's Hierarchy Configuration.

All issue types you import, must be mapped to a hierarchy level. You find this in the Administration section of the Portfolio addon (In the JIRA menu: Portfolio / Administration and then Portfolio Hierarchy Configuration.

If it's not that or you can't figure it out, do what the error message says and send the details of the error to Atlassian support, so they can help you figure out what went wrong exactly.


Tags: advanced-roadmaps

release
Assignee to team member does not work on the scope panel in Portfolio for JIRA
Asked by Gonchik Tsymzhitov:

Hi!

I have a small question:

If I assign manually team member issue on the scope panel in Portfolio JIRA panel.

Issue in JIRA project has not assignee.

Then I have seen in the report with grouping per person, on the another team member.

I tried to change all Issue assignee import level nothing changes.

Expect: The member to be set in the panel view  
Actual: . It is not set and get message if I click on the members button "No constraints - Automatic assignment based on availability."


Answers:
author: Rakesh Chauhan
body: Can you simplify your question. Not able to understand the problem

comments: author: J?rg Witthaus
body: Hi,

I am having the same issue as mentioned above.

I will try to simplify the description:

I have 2 projects with a Backlog in Jira with all Stories assigned. In Portfolio I have one single shared software team responsible both projects.

After importing that boards into Portfolio the assignees have been changed automatically. "Sceduling options" is set to "story". Changing the will not map assignees from Jira 1:1 to the team members.

Do you have any idea why?

best regards


Tags: advanced-roadmaps
Multiple version of a product to plan
Asked by JulienFritsch:

Hi, we are newly using the Portfolio and we are on our way to implement it product by product \& team by team. And we have a decision to take on how to implement the plan for multiple version work when done by a single team.

Let me explain we have the product team A which is working on the product Z, which has 3 maintained version A1, A2 and A3 and a future new version A4. So far, in their backlog, specific for product Z, each version exists as 'versions' and the backblog of issues are assigned to each fix version and grouped in sprint dedicated to a single version and to each time a specific lengh. So this means for instance :

Sprint 11 - version A1 for 2 weeks for team A

Sprint 12 - version A2 for 1 week for some members of team A

Sprint 13 - version A3 for 3 weeks for team A

Sprint 14 - version A4 for 4 weeks for team A

Sprint 15 - version A1 for 1 week for some members of team A

...

But, in the Portfolio, the most important plan we want to follow and manage carrefully is the version A4 since it's where new features are. The 3 other versions are maintenance version and we do the max per sprint to solve all the bugs. I'm not sure yet, we'll get all those bugs in the Portfolio plan.

Now that we'll be using the Jira Portfolio module, I was wondering what would be the most ideal way to manage those sprint \& versions. At the moment, I do have the version A4 scope in the plan and I'm getting the teams. But once we'll get to the estimates and planning, I know that I'll face an issue, since the plan won't be continuous (interruption with the maintenance sprints), so I wanted to brainstorm this here with those that might either have some experience or idea how to best manage this.

Regards.


Answers:
author: JulienFritsch
body: So far, I'm thinking to get the maintenance sprint as Epic/Issues and assign the full team on it in order to generate some alert on the capacity. But I'm curious to see if anyone solved this problem already.


author: JulienFritsch
body: Has anyone any idea for this question ?


Tags: advanced-roadmaps
Assigning sprints to teams in JIRA Portfolio
Asked by Jaros?aw ?wierk:

Hi,

we have the following situation when using Portfolio 2:

* the team consists of 3 scrums, in portfolio they are represented as 3 scrum teams
* all scrums work on the same JIRA project (so share the backlog)
* each scum has dedicated sprint to keep the commitment clean

Now when trying to use Portfolio 2.0 the plan properly imports the sprints from the single board (which is used as source) but it is not able to resolve the fact that the sprins are happening concurrently. Note that it seems not to be possible to define the dates for the future sprints (which weren't started yet). As result automated scheduling is not usable.

Is it possible to configure e.g. mapping of the sprints and the agile teams or any other way to tell Portfolio plan to align the sprints properly?

Thanks in advance

Jarek


Answers:
author: Mark Donaghy
body: Have you tried to create separate boards for each of the concurrent sprints and then using each board as a source for the plan?

comments: author: Jaros?aw ?wierk
body: That unfortunately does not work - the boards show automatically the sprints that the issues inside are put on. In theory this probably is the solution but means I need to separate the backlog for each scrum (so that the board does not show issues from the same JIRA project but somehow labeled as belonging to other SCRUM. And this is sth I would like to avoid - in general 3 scrums are planning their work separately but it does happen that we switch some of the stories to other scrum - depending on the progress and priority of the issues (if one scrum is faster and others have delay then they take over high priority issues before working on their original lower priority items). The the trick is to share the backlog but somehow properly sequence the sprints...


author: Mark Donaghy
body: Another alternative is to use three different JIRA projects and to bring them together under a portfolio program. I am using that successfully.


Tags: advanced-roadmaps
How do i import closed story to portfolio?
Asked by Vivian Lin:

I am trying to import projects into portfolio and need to include closed issues so that we can show progress made thus far prior to using portfolio. I can't seem to get closed stories to show up in the import screen whether i'm importing from a project or filter. the filters do not filter based on status so when searching for filter i can see closed stories, but not in portfolio. please help.


Answers:
author: Allard van Helbergen
body: Hi [@Vivian Lin](/t5/user/viewprofilepage/user-id/1126072),

As Portfolio for JIRA is a forward planning tool, the default filtering inside a plan is set to filter done issues that are older than the current sprint. You can see these filters (and their default settings) under the more button in the filter menu.

Have a look to see if changing those filters helps you.

This page here, will detail the other filters that exist inside of Portfolio.   
<https://confluence.atlassian.com/jiraportfoliocloud/using-scope-filters-828785257.html>

Cheers,  
Allard


Tags: advanced-roadmaps