youngmon/atlassian-qna huggingface dataset:
How to Automate existing and upcoming Jira Stories?
Asked by kumar:

Hi all,

I already asked similar question, but some info was missing. Therefore, I am asking it once again with more info.

I need to automate the jira process, so that if the jira issue do not/did not contain specific file attachments, that jira ticket should be rejected.

But trick is, the above task needs to be done for both existing jira issues and the newly created ones.

Based on the rejection of jira issues, we have some more automation steps/analysis steps of the rejected jira issues.

I have done some research, based on my research, I have found below solutions:

- State machine based Jira Automation

- ScriptRunner using Groovy

- FAST API/Python script

But the problems is we do not want state machine based jira automation, due to that facts that there are already tons of existing jira issues, so that those issues states can not changed.

Therefore, I am looking for optimal solutions, which should also fit our future plan/goal.

If there are any AI based solutions, I am open to hear your suggestions as well.

Thanks in Advance


Answers:
author: Shawn Doyle - ReleaseTEAM
body: I'd tackle this in two steps. I call this fixing the hole in the boat before bailing out all the water.

**1. A workflow condition to reject new Jira issues that do not have your required documents**

Once in place this will stop any new issues that do not meet your requirements.

**2. A script to look for existing Jira issues that do not have your required documents.**

Step 2 can be with either Scriptrunner, REST API or even automation. You would run this manually initially to get all existing non-compliant issues. It can then be run periodically to ensure no new issues were missed by step 1.


Tags: cloud

jira-cloud
Closed Ticketsq
Asked by Chris Rhodes:

How do I create a dashboard or generate that shows number of tickets closed/resolved by each support person?

Thanks

Chris


Answers:
author: Trudy Claspill
body: Hello [@Chris Rhodes](/t5/user/viewprofilepage/user-id/5488827)

Welcome to the Atlassian community.

Do you consider the Assignee to be the person that Closed/Resolved the issue, or do you want to count based on the person who actually executed the transtion?

You could create a filter to retrieve all the issues in the Closed/Resolve status of interest.

Then in a Jira Dashboard you could add a Two Dimensional Filter Statistics gadget. Select Status for the X Axis and Assignee for the Y Axis.

![Screenshot 2024-08-05 at 9.32.18?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/340056i4BE1B561EFB36432/image-dimensions/226x349?v=v2 "Screenshot 2024-08-05 at 9.32.18?AM.png")

You would end up with output something like this, showing only the Statuses that you had included in your filter:

![Screenshot 2024-08-05 at 9.34.58?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/340057i7CA335732A402033/image-size/large?v=v2&px=999 "Screenshot 2024-08-05 at 9.34.58?AM.png")


author: Shawn Doyle - ReleaseTEAM
body: Use a Filter Results gadget on a dashboard. There are several posts explaining how to do this, however, it's pretty straightforward.

<https://community.atlassian.com/t5/Jira-questions/how-to-add-gadget-in-jira-dashboard-to-see-issues-which-are/qaq-p/2679157>

<https://community.atlassian.com/t5/Jira-questions/Filter-for-closed-open-user-stories-bugs/qaq-p/2324350>

<https://community.atlassian.com/t5/Delete-if-empty-2/Jira-reporting-Number-of-issues-closed-by-the-user/td-p/1461722>


Tags: cloud

jira-cloud
Assign tickets from JSM to JIRA software
Asked by Dilli Babu:

Currently i've set-up JSM for the customer support.  

Once we received ticket from customer, I have to assign the ticket to developers which there are in the JIRA software project.


Answers:
author: Samuel Gatica
body: Hi [@dilli babu](/t5/user/viewprofilepage/user-id/1266408)

There is a new feature available in JSM called [Developer escalations](https://support.atlassian.com/jira-service-management-cloud/docs/what-are-developer-escalations/)

"Developers can be added as collaborators to your project in Jira Service Management. Collaborators are a specific type of licensed users in your Jira site with whom agents in Jira Service Management work. They usually belong to your organization's internal teams, and occasionally assist agents with customer requests by making internal comments.

Once the developers investigate the underlying reason for the customer issue, they can share their findings by adding internal comments."

Another approach is to create an integration between your JSM and JSW project, please check

[A helpful guide to automate comment copying across JSM, JSW, and JWM projects](https://community.atlassian.com/t5/Jira-Service-Management-articles/A-helpful-guide-to-automate-comment-copying-across-JSM-JSW-and/ba-p/2665332)

Hope this helps

Best regards

Sam


author: Trudy Claspill
body: Hello [@Dilli Babu](/t5/user/viewprofilepage/user-id/5552422)

Welcome to the Atlassian community.

Only users that have been granted the JSM Agent level of Product Access and added to the specific JSM project will be able to change the status of JSM issues. Users that have only a Jira Software license will only be able to add internal comments to the JSM issues.

Can you make the developers JSM agents, to enable them to do more than just add internal comments to the JSM issues?


Tags: cloud

jira-service-management

jira-service-management-cloud
'Deal ID' search no longer possible?
Asked by Mireille Meerleveld:

Dear,

There are several search options within Jira Projects: by project title, customer name and until recently also via a so-called 'deal ID' in our organization, which is a custom field, on the tab 'project'. Since a while no more projects are found based on Deal ID. How can this be fixed?

If more information is needed, please let us know.

Awaiting your response,

Mireille Meerleveld e/v Glimmerveen


Answers:
author: Samuel Gatica
body: Hi [@Mireille Meerleveld](/t5/user/viewprofilepage/user-id/5560988)

Welcome to the community!

Could you please provide some screenshots demonstrating how you are conducting these searches?

Best regards

Sam

comments: author: Mireille Meerleveld
body: Dear Sam,

Many thanks for your reply! My apologies for this late response.

We enter the deal number (reference) at the top right after which only the issues appear in which this deal number is listed. ![Schermafbeelding 2024-08-13 091303.png](https://community.atlassian.com/t5/image/serverpage/image-id/341447i8055852ED45B788A/image-size/large?v=v2&px=999 "Schermafbeelding 2024-08-13 091303.png")


Tags: cloud

jira-cloud
I am unable to import test cases due to an error
Asked by Parth Modi:

Unable to import test case due to an error although all the fields I have configured seems correct in the CSV file. Also I have saved CSV file with UTF-8 encoding.

![image.png](/t5/image/serverpage/image-id/340000i495DBD7DFE763D06/image-size/large?v=v2&px=999 "image.png")

Still I am receiving below error

{ "errors": \[

{ "elementNumber": 0, "errors": { "customfield_13958": "Field 'customfield_13958' cannot be set. It is not on the appropriate screen, or unknown." } },

{ "elementNumber": 1, "errors": { "customfield_13958": "Field 'customfield_13958' cannot be set. It is not on the appropriate screen, or unknown." } } \], "issues": \[\], "warnings": \[\]

}

Can someone please help me debug this issue.


Answers:
author: Parth Modi
body: Mainly priority icons were causing the problem. Once, I removed them import started working.


author: Laurie Sciutti
body: Hi [@Parth Modi](/t5/user/viewprofilepage/user-id/5561010) and welcome to the Community! The error indicates that one of the fields you are mapping in the import does not exist on the screen for the project you are importing to. I would recommend opening your Screen Scheme, finding the Create Issue Screen for the Test issue type and checking that all mapped fields exist on the screen. HTH


Tags: cloud

jira-cloud
Getting error as "There is no scheduled epic in the current result set"
Asked by peter decosta:

After creating a plan in the portfolio getting following error:

"There is no scheduled epic in the current result set" {#toc-hId-1789727896}
----------------------------------------------------------------------------

While Epics \& Stories are appearing under Scope tab.


Answers:
author: somethingblue
body: Hi Peter,

Take a look at the Communities post [Solved: The current scheduling result does not contain any epics](https://community.atlassian.com/t5/Jira-questions/The-current-scheduling-result-does-not-contain-any-epics/qaq-p/159593). Two common reasons this can occur is as follows:

* There are no resources available who can be assigned with the epics (e.g. no teams/team members are defined or insufficient team velocity to fit anything in)
* The epics don't have an estimate (an epic can have an estimate by itself while it has no child stories, otherwise it is the total estimate of the child stories)

If the epics cannot be scheduled, they are highlighted in red in the backlog table after pressing "Recalculate", and when hovering over the items title (the first column), there is a tooltip giving more details on why it could not be scheduled.

Let us know what you find and we'll go from there.

Cheers,

Branden


Tags: advanced-roadmaps
How do I set Later release to start relative to previous release date?
Asked by Heather Cronbaugh:

Based on knowledge base articles, the Later release is supposed to start after the last created release date. However, mine is set to start "as early as possible" which is scheduling work concurrently with work prioritized into name releases.

ASK \| How can I change this setting so it doesn't start until named releases end?


Answers:
author: david.hiatt
body: same issue, nearly two years later. disappointing you got no guidance or response.


Tags: advanced-roadmaps
Modify scheduled start and end dates in portfolio to use different date fields for capacity planning
Asked by Narbeh Yousefian:

In portfolio there is 2 fields called **scheduled start** and **scheduled end**. How is this configured? I tried to look in my admin settings but these fields are not in the available fields. Is this something specific to portfolio?

I have custom start and end dates for my project Epics which I would like to use in Portfolio, why is this not an option? And lastly, what is the point of adding in custom fields into Portfolio if you can't use them for portfolio management? The whole point of this view is to manage dates, why is the schedule date field not editable? And why cannot you use your own custom dates instead?

----

edit:

So it looks like Portfolio is only useful if you run SCRUM and build "stuff" based on **Release**. Meaning if you run Kanban with start and end dates but no Release, Portfolio is useless.. So frustrating..


Answers:
author: Martin Sturm
body: Hello Narbeh,

you are right, scheduled start and scheduled end are specific to Portfolio and are not editable purposefully. The reason for this is that they hold the start and end dates calculated by Portfolio's scheduling algorithm which is based on the issue estimates, available persons, dependencies and so on.

The reason this field is not available in Jira is that it is very plan specific. An issue could be available in multiple plans where people for example plan some scenarios or the like. Also the value would change whenever someone in some plan triggers a calculation.

It is generally possible to add Jira custom fields to Portfolio if you click on the plan settings dropdown (next to the title) / Configure / Custom fields. Then you can add them to the plan and in the Scope table as a column.

If you want to see your dates also in the visual schedule you could think about using Portfolio's target start and target end fields. These are available in the Scope table as well and if you switch from "Schedule" to "Target schedule" after a triggering a calculation you will be able to see the target dates in contrast to the best scheduled dates found by Portfolio given your plan data. Note however that these fields are also plan specific and therefore specific to Portfolio.

Cheers, Martin

comments: author: Narbeh Yousefian
body: Thank you Martin. Appreciate the response here. Managed to figure it out in the end with your help. Cheers


author: Mehrshad Setayesh
body: Hi Martin,

According to image below, if you move the story to an earlier release, the release's end date should overwrite the computed scheduled end date. However, its not happening in my case. Do you know why?

Thanks

M.![Scheduled_End.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/32333iC00115FDA1FAC574/image-size/large?v=v2&px=999 "Scheduled_End.jpg")


Tags: advanced-roadmaps
Re: can I filter by project category?
Asked by Nic Brough -Adaptavist-:

Yes. JQL is "category = ..."


Answers:
author: Nic Brough -Adaptavist-
body: It's a quiet gem of a function which stopped my only real attempt to write an add-on I could sell - I wrote something that let you search by category in JIRA 3, and then JIRA 4 did it for me!


author: Leo Cortez
body: Can I include the category as one of the columns? It does not appear in the list of columns available


author: Marta Ogonovska
body: [@Nic Brough -Adaptavist-](/t5/user/viewprofilepage/user-id/781454) thanks a lot :)


author: Drew Angell
body: [@Nic Brough -Adaptavist-](/t5/user/viewprofilepage/user-id/781454) Interesting, I'll play with this, thanks!


author: Nic Brough -Adaptavist-
body: JQL searches for issues, not projects, but you can stick a search for all issues through a "filter statistics" gadget and report on projects to get a count of issues per project (which then gives you the list of projects)


author: Drew Angell
body: What if I just want a list of the project names in a particular category so I can display them in Confluence?


author: Leo Cortez
body: Thanks.


author: Nic Brough -Adaptavist-
body: I'm afraid you can't without a bit of code (yet)


author: Deborah Genevro
body: Wonderful. Thanks so much. You just saved me a lot of time!


author: Seth Pritikin
body: Perfect, thanks so much, Nic!
What sets the "Scheduled start" date?
Asked by David Doria:

In the Scope panel, issues have a column called "Scheduled start". Unlike "Target start" and "Target end", this does not seem to be editable. Presumably this date is getting pulled from some information on the actual issue - is there a way to change this date?


Answers:
author: Surbhi Soni
body: Hi [@David Doria](/t5/user/viewprofilepage/user-id/1159533) , Its probably late and already have answer to it but still want to share my findings.

* The "Scheduled Start" \& "Scheduled End" date picks up data from the "Target Start" \& "Target End" dates respectively.
* "Target Start" \& "Target End" are Locked Date field specifically created for Portfolio in JIRA.

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

* One way is you add both of the fields in the JIRA tickets screens and then update the dates.

OR

* In Plan, you can choose any other custom date field suitable to display the start and end date in configuration Setting of Plan.
* So by this you are basically telling Plan to consider the custom date field.
* Make sure the custom dates you select here is**present in all issue screen \& is populated**.

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

Note: I tested this in JIRA DC version 8.20.


author: Florian Friedebold
body: Have you tried editing the start date of your first or concerned 'Version' resp. 'Release' ?That's accessible via your board, where you can also see your epics.

If you have the dependencies set up properly between your epics and tasks, the 'Scheduled Start' should recalculate to a new date.

Best regards


author: Victor Florin Pana
body: <https://confluence.atlassian.com/jiraportfoliocloud/scheduling-behavior-828785428.html>

comments: author: David Doria
body: So is the answer "no"? There seem to be some things, like the list of sprints that this issue has been in, that are part of the "history" and cannot be changed - is this correct? Thew view for "Scheduled range: Full" is goofy because of this, where something extends back many months just because it has been pushed to future sprints a few times.


author: Thomas
body: The scheduled start and end columns you are mentioning are not part of a Jira issue data and represent the scheduling calculation result. It is not possible to change those currently.

More generally the values given by the calculation are not modifiable as they represent the idealistic dates decided by Portfolio for the data currently in your plan.


author: Hillary Moore
body: Which date fields are used by the scheduling calculation? Which dates fields have to be populated in order to calculate a schedule?


Tags: advanced-roadmaps
Billing for the Portfolio Addon
Asked by Greg Jordan:

Hi,

I am looking to incorporate the Portfolio Addon for our cloud instance of JIRA. I was wondering whether the charge per month relates to all active users?

Is there a way that we can only pay for those users who are given permissions to use it?


Answers:
author: Shannon S
body: Hi Greg,

The number of users you're charged for in Jira Portfolio must match the number of users you have in your Jira Software instance. It's not possible to pay for only specific users.

For more information, have a look at this page:

* [Portfolio for Jira Licensing](https://www.atlassian.com/licensing/jira-portfolio#cloudlicenses-1)

Kind regards,

Shannon


Tags: advanced-roadmaps
Do portfolios support Kanban sources?
Asked by Dave Hearne:

I can include a Kanban board as an issue source when making a plan. However, Epics do not come across. Further, since Kanban stories do not have "size" it seems that the Portfolio is unable to develop a schedule.  

Am I missing something?


Answers:
author: Dave Hearne
body: They do. Turn out that Epics have components. If the components do not match the board components, they don't get pulled into Portfolio with the issues.


Tags: advanced-roadmaps
Adding an existing Epic from a scrum board to a Jira Portfolio Plan
Asked by Leti Fanning:

I have created a Portfolio plan and added in my scope of Epics and then realized that I forgot to add 2 existing JIRA board Epics to the plan. Portfolio allows you to remove from the plan or 'create new' but there's no selection for adding an epic from the same source scrum board. How do I make this happen?


Answers:
author: somethingblue
body: Hi Leti,

Others have had success with this by going back through the Configure Issue Sources without making any changes along the way. Take a look at [Solved: I excluded some epics and stories from my plan but now I want to add them back](https://community.atlassian.com/t5/Jira-questions/I-excluded-some-epics-and-stories-from-my-plan-but-now-I-want-to/qaq-p/85217) for the steps one user took.

Cheers,

Branden

comments: author: Leti Fanning
body: Thank you Branden,

I can see the additional Epics, if they have been tagged to a release. What causes the problem of not being able to see the stories under an Epic? I see them in JIRA, under the EPIC, and all assigned to the same release. The EPIC is In Progress with 2 stories under it In Progress and the other 2 Ready. What can I do to trigger them to get pulled into my Portfolio plan?


Tags: advanced-roadmaps
How to account for waiting before starting a task (i.e. waiting for delivery of item)
Asked by Mahmood Hikmet:

In our team, sometimes we ship things between locations. I need the item to reach the destination before I can start working on tasks that involve that item (i.e. waiting for a circuit board to be delivered).

If I know delivery will take about 5 days, then I don't want any of the blocked tasks to start until 5 days from now. If the item DOES get delivered early, or there's a delay in delivery, I want to be able to see the effect of that.

I thought about setting up a "release" for when the item arrives. But then how do I dynamically control the beginning of work on the following release to coincide with the end of the current one? Otherwise I can set up a task for "waiting for delivery", however, this throws off the scheduler, because then I have a team member literally waiting around for a delivery rather than doing some other work in the meantime.

How do I make this work in Portfolio?


Answers:
author: Mahmood Hikmet
body: To all future internet people, I found an answer but only in the Portfolio Server documentation. This will work great!

<https://confluence.atlassian.com/jiraportfolioserver/time-constraints-715263082.html>

Just in case that link goes dead, you are able to add an "Earliest Start Date" for an issue. So you either modify the "earliest start date" of whatever is being blocked, OR you can create a task for "delivery" and set its estimated time to 0 and adjust the "earliest start date" for it as you learn more about when it will arrive to have everything else schedule as portfolio does.


Tags: advanced-roadmaps
JIRA Portfolio release field
Asked by Ricky Aladort:

What JIRA field does Portfolio use to calculate releases? And is this a configurable option? For example, if fixed version is the field, can I choose another field in JIRA for releases?


Answers:
author: Thomas
body: Hi [@Ricky Aladort](/t5/user/viewprofilepage/user-id/831469),

Portfolio uses the fixVersion field that comes with Jira, it is currently not possible to use another field.

I am definitely curious about your situation and use case, feel free to describe it a bit if you're willing to help understand why this configuration would be useful / necessary in your case.

Cheers,

Thomas

comments: author: E K
body: Hi Thomas,

I have similar question as [@Ricky Aladort](/t5/user/viewprofilepage/user-id/831469) .

My situation is as follows: we have sprints of 3 weeks and at each sprint we do a release. We also have a milestone release which can contain one or more sprints.

If I define in protfolio a milestone release (say containing 4 sprint releases), then this is added to JIRA as a "release".

But in JIRA, I will also release each sprint, which should have a fixed version for the issues/user stories fixed/completed in that sprint. I can use the milestone release, but that is not perfect because all sprints will have the same fixed version.

How to handle this situation?


author: Thomas
body: Hi [@E K](/t5/user/viewprofilepage/user-id/2728206) ,

We are looking at both improving how we handle the conceptual difference of milestone/releases, and supporting multiple fixVersion per issues in Portfolio (<https://jira.atlassian.com/browse/JPOSERVER-1931>).

For now, you could look at not assigning the milestone release to issues, rank it after the last sprint release and set its release start/end date to be after the previous release ended or with a fixed date. You will require to enable the "Show empty releases" on the timeline still.

Hope that helps,

Thomas.


author: Paulo Gaspar
body: Is this really going to be fixed? Soon? I spent so much time trying to figure out why no issues (at all) were showing in Portfolio and the reason was the lack of the fix version field. Had to dig deep into the internet.

Also, it would be really cool it portfolio didn't depend on releases and versions. Not every team works like that. For example, for us, every sprint is a release, so we don't even configure releases in jira.

Thank you


Tags: advanced-roadmaps