youngmon/atlassian-qna huggingface dataset:
How to Fetch Linked Issue's Status if Linked Issue from a Different Project (Using Simple JQL)
Asked by Avik M:

I have a (hopefully) simple question.

I use Power BI Jira Connector to pull and display JIRA from my Project ("ABC"). Now various tickets in my Project are linked to Issue Keys from other projects. So when I am pulling data by using :

**project = "ABC" ORDER BY created DESC**

then unfortunately, I dont get to See the Status of those linked issues which are not of my project. Say for Example, ABC-111 is having a "Has to be done After" "XYZ-123" link. In such case I dont see the status of XYZ-123 in my Power BI.

So basically what I needed is:

**project = "ABC" OR issueFunction in linkedIssuesOf("project = 'ABC'") ORDER BY Key DESC**

But unfortunately, the above Syntax works with ScriptRunner but not with Power BI Jira Connector's JQL, which I guess is offering simple / default Jira Search operations.

Any Idea - how to overcome this?


Answers:
author: Laura Campbell _Seibert Media_
body: Hi [@Avik M](/t5/user/viewprofilepage/user-id/5586072) and welcome to Community.

I'm not a Power BI expert, so I don't know if you'd be able to configure what you need with a bit of help from the team behind the product.

However, I do know that displaying details of linked issues is what [Dependency Mapper for Jira](https://marketplace.atlassian.com/apps/1221796/dependency-mapper-for-jira-visualization-and-management?hosting=cloud&tab=overview&utm_source=atlassian-community&utm_medium=referral&utm_campaign=question-2805400) is great with (btw, I work with the team behind the app). The app has 11 different charts to visualize dependencies between issues. The product owner is currently working on adding a feature to see the status of linked issues, and would be interested in getting your feedback. If you have 20 minutes and want to see if the app could be a good fit, you can [book a call with the Product Manager Brad Quirk](https://calendly.com/brad-quirk/quirk-discovery-call).

comments: author: Avik M
body: Hi [@Laura Campbell _Seibert Media_](/t5/user/viewprofilepage/user-id/3327113)

I clearly stated my requirement already and its simple demand - That I should be having a JQL to query "Issues and its linked issues". I can easily do that by using external plug-ins like script runner etc. but there are many applications and add-ons (example, as I mentioned: "Power BI Jira connector" which only supports pure "JQL" and over there we are stuck.

So, you got my question wrong - I'm not looking for another plug-in...


Tags: cloud

jira-cloud
Board views - issuetypes != Story
Asked by Gleica:

In board views, when a story has an epic linked, the cards appear linked when they are in the same status (Story + Epic).

Why doesn't the same happen with Tasks, Bugs or other types of items at the same level as stories?


Answers:
author: Trudy Claspill
body: Hello [@Gleica](/t5/user/viewprofilepage/user-id/5558412)

Welcome to the Atlassian community!

Can you provide screen images to show us what you are seeing, both for the Story + Epic, and for a Task/Bug/Other type that is not showing in the same way?

comments: author: Gleica
body: it's like this

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

I would like it to stay like this

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


author: Trudy Claspill
body: Hello [@Gleica](/t5/user/viewprofilepage/user-id/5558412)

What is the project type for the YMD project? Get that information from the View All Projects page under the Projects menu.

What you have highlighted in the second image is a Story and its Sub-task. Subtasks will display nested under their parent issue. This is a special feature of Subtasks. The same feature is not available for Epics and their child issues.

If you want to group child issues under their parent Epics you would need to change the Group By option for the board to Epics.


Tags: cloud

jira-cloud
How do I define the summary of the test execution created using /api/v2/import/execution/junit?
Asked by Pratt_ Trenton:

I have a Cypress test suite that creates an xml report upon completion. I then import those test results using the /api/v2/import/execution/junit endpoint. This is functioning, but the resulting test execution will have a summary like "Execution results \[1725561773655\]". What does this code correspond to? And is there a way I can define the summary automatically?

This is all happening in a Gitlab CI. Best case scenario is that I could include a Gitlab predefined variable in the Test Execution summary so that I could trace the Test Execution back to the merge request it was testing.


Answers:
author: Stefan Salzl
body: Hi [@Pratt_ Trenton](/t5/user/viewprofilepage/user-id/5586041) - welcome to the community,

unfortunately it's not possible directly within the same call.

I managed to do a similar thing in a github action by creating a test exdcution issue via the native jira rest api and saving the key in a variable right before importing the cypress test results. I could then use the variable within the import call.

Let me know if this is helpful or if you have any further questions.

Best  
Stefan

comments: author: Pratt_ Trenton
body: Thanks for the help!


author: Stefan Salzl
body: [@Pratt_ Trenton](/t5/user/viewprofilepage/user-id/5586041)

it?s my pleasure ;)


Tags: cloud

jira-cloud

junit

test-management

xml

xray
How do I get story points completed within the sprint and outside the sprint
Asked by Manak Pushkarna:

I am trying to create a Velocity Widget on one of the JIRA Dashboard. While defining the underlying JQL query, I am struggling to find a way to get story points completed within the sprint and story points completed outside the sprint.

We have recently migrated to JIRA Cloud from On-Prem Jira.

In On-Prem JIRA, this was possible using

issueFunction in completeInSprint(". I am trying to find a substitute in JIRA Cloud.


Answers:
author: Danut M _StonikByte_
body: Hi [@Manak Pushkarna](/t5/user/viewprofilepage/user-id/5586038),

You can see the issues and the number of story points completed in the Sprint Report. The report shows also the issues completed outside of the sprint.

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

If you want to use a gadget instead of report, you could search on Atlassian Marketplace, but I'm afraid that there is no app that can display issue completed outside of the sprint.

If you consider using an app, our [Great Gadgets](https://marketplace.atlassian.com/search?query=stonikbyte%20great%20gadgets%20agile) app offers a **Team Velocity gadget** that can display the story points completed in each sprint, but not also the ones completed outside of the sprint.

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

Hope this helps.

Danut


author: YY Brother
body: Hi [@Manak Pushkarna](/t5/user/viewprofilepage/user-id/5586038)

Welcome to our Community.

issueFunction is not the native JQL funciton in both On-Prem and Cloud Jira. You maybe need to install scriptrunner app to get this function work in Jira Cloud.

Hope it helps you.

Thanks,

YY?

comments: author: Manak Pushkarna
body: Thanks [@YY Brother](/t5/user/viewprofilepage/user-id/4083879) . Can you suggest an alternate to my original problem to find story points completed within a sprint and outside a sprint?


author: YY Brother
body: Would you have a try Sprint Reviewer App? Only the story points completed within the sprint are counted as real completed points.

<br />

[https://marketplace.atlassian.com/apps/1233252/sprint-reviewer-pro?hosting=cloud\&tab=overview](https://marketplace.atlassian.com/apps/1233252/sprint-reviewer-pro?hosting=cloud&tab=overview)


Tags: cloud

jira-cloud
What is the use of the "customisation" folder in jira-home folder?
Asked by Svea Michel:

What is the use of the "customisation" folder in jira-home folder?

Is this folder only for backup to store customized config files before upgrades?

We are using Jira in ia a container via Podman. The container image is a standardized one from a provider. Customizations are done with ansible. For reasons I need to modify the cipher settings in the server.xml file. A modification inside the non-persistent Jira installation is useless because after a full restart of the container the files will be initialized again.  
A possibility I've successfully tested is to mount the particular file from a persistent location to the non-persistent location but that could cause trouble when Jira is updated (aka new container image is pulled) and settings in the mounted config file doesn't fit to the new version.

I haven't found any proper explanation for what the "customisation" folder is. Would it be possible to store modified files there and Jira copies them automatically to the right non-persistent location when the container is started?


Answers:
author: Matt Doar _Adaptavist_
body: I don't recall for sure but I thought it was some way to add info to a support zip, containing all the files that you have changed. That is, the files in that directory are snapshots, not used by a running Jira instance.

comments: author: Matt Doar _Adaptavist_
body: In a fresh Jira 10.0.0 local install I have the jira-application.properties where I set JIRA_HOME and a bunch of package-lock.json files from various core jar files


Tags: data-center

jira-data-center

jira-server

server
Why is the rule not executing consistently?
Asked by In Heo:

The rule is designed to execute every minute to check if a ticket was created 1440 minutes (exactly 24 hours) ago, but not beyond 1441 minutes. However, there have been irregular time gaps in its execution, indicating it's not functioning as intended. What could be the potential cause for this inconsistency?

![Screenshot 2024-09-06 at 11.47.07?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/345998iEFB7DDCA31833F6C/image-size/large?v=v2&px=999 "Screenshot 2024-09-06 at 11.47.07?PM.png")


Answers:
author: Aron Gombas _Midori_
body: [@In Heo](/t5/user/viewprofilepage/user-id/5458237) It is an implementation detail, but in the background "pending executions" will be put to a *global* queue (of work-to-be-done), and a pool of workers is working on them.

In this case, your scheduled execution will be put the queue, but it is impossible to tell how many other executions are also waiting in the queue. All in all, the latency of actually starting your scheduled execution is impossible to estimate. It will vary depending on the load.

Simply, you *should not* rely on the precise start time. There is no guarantee for that. You have to accept the random latency.

comments: author: In Heo
body: Totally understand the situation now. Appreciate the details!


author: Michel Neeser
body: Hi [@In Heo](/t5/user/viewprofilepage/user-id/5458237)

Is your automation rule running for more than one minute? A scheduled rule can only run once at a time. So if the run time is more than one minute, the next executions of the same rule may be postponed or even skipped.

comments: author: In Heo
body: Hi [@Michel Neeser](/t5/user/viewprofilepage/user-id/1828853)

thanks for your input. I've considered the scenario you mentioned, but it seems the execution time consistently takes less than 1 second.

![Screenshot 2024-09-07 at 12.01.45?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/346000iACBE0C3674C75387/image-size/large?v=v2&px=999 "Screenshot 2024-09-07 at 12.01.45?AM.png")


author: Michel Neeser
body: [@In Heo](/t5/user/viewprofilepage/user-id/5458237) If I recall correctly, the minimum scheduling interval used to be 5 minutes. While I know that this is no longer the case, I can imagine that, from a technical standpoint, there might still be some limit in place to prevent excessive system load. It may be worth asking [Atlassian Support](https://support.atlassian.com/contact/) regarding this.


author: In Heo
body: Alright, but isn't this something for Atlassian support...?


author: In Heo
body: then do you think adjusting the rule to run every 5 minutes would ensure it executes consistently every 5 minutes?


author: Michel Neeser
body: [@In Heo](/t5/user/viewprofilepage/user-id/5458237) I would give it a try, at least. I assume that longer intervals lead to greater consistency due to potential technical limitations in the background.


author: In Heo
body: Haha, I've updated the rule to run every 5 minutes, but it's still showing inconsistency with larger time gaps---ranging from 5 to 8 minutes.


Tags: cloud

jira-cloud
Remaining time <-> Due Date related
Asked by vincenzo_spatafora:

Dear Community,

I would like to create an automation rule with the following logic:

1. (Trigger) When the user logs the time spent in an issue
2. (Condition) The issue is a sub-task
3. Take the remaining estimate value of the sub-task's parent
4. Take the parent due date and work-out if there is still sufficient time to meet the due date
5. If not, a warning email is sent to me

Is that first of all possible to implement?

If so, could you please help me out as I don't know the syntax to use.

Thanks in advance,

Vincenzo.


Answers:
author: Ekaterina Smykova
body: Hi [@vincenzo_spatafora](/t5/user/viewprofilepage/user-id/5485027) ,

There is built-in function in "Time tracking" to include Logged Work from Sub-tasks into "parent" issue: ![time tracking.png](https://community.atlassian.com/t5/image/serverpage/image-id/345995iCD0B9518966E6474/image-size/large?v=v2&px=999 "time tracking.png")

I believe that might work for the first part of your question.

For the mail part you can create a JQL filter and subscribe to it where you can choose times when it can be sent:

"project = XXXX and remainingEstimate \<= 5", depends on what amount is seen as indicator of not sufficient time left.

comments: author: vincenzo_spatafora
body: Thanks [@Ekaterina Smykova](/t5/user/viewprofilepage/user-id/1617933).

But how can I work-out via the automation rule if the remaining time is still sufficient to meet the due date.

Cheers, Vincenzo.


author: Ekaterina Smykova
body: [@vincenzo_spatafora](/t5/user/viewprofilepage/user-id/5485027) , just added additional part to the original message :)


Tags: data-center

jira-data-center
Pros and Cons of estimating story points at a task level
Asked by Garth Bond:

I have just joined an organisation that do all their estimations at a task level. I.e. there is no story point estimations, only at a task level. They say that had to do this because Jira could not show their management the actual work for work done to date or something like that.

What I would like to know from a Product prospective is how this effects the use of Jira overall as a result of this. They use Excel for Sprint Planning and it seems a waste given this is what Jira is designed to do.

Please provide me with your insights and recommendations for why this many not be a good idea and why?


Answers:
author: Trudy Claspill
body: Hello [@Garth Bond](/t5/user/viewprofilepage/user-id/5585985)

Welcome to the Atlassian community!

It is unclear to me what you mean by "at the task level" in the context of the company's Jira configuration.

The default issue type hierarchy for Jira is:

```
Epic (level 1)
|-- standard issues (level 0) i.e. Story, Task, Bug
    |-- subtask issues (level -1)
```

For Sprint Velocity and burdown/up native reports the information is based on estimations used at Level 0 - Standard Issues.

What level is the company's "task" at? Is it not at Level 0?

comments: author: Garth Bond
body: No they don't estimate the story points for a requirement. What they do is take the Story point and break it down into sub-tasks which are assigned to the development team. They estimate the sub-tasks not the story as a whole. I think this is the reason none of the Jira standard reports work.

I cannot pin-point exactly why they do this. The only thing I can gathers is that they need full visibility in everything that has been done, not just when a story is completed for some reason.

Does this seem odd to you?

Regards

Garth


author: Trudy Claspill
body: The primary argument against this when using Jira is that the native burndown/up reports won't support it and can't be forced to support it. That would require a third party app that would add to the overall cost of the system. And the methodology they are using has prompted them to use a different tool for sprint planning rather than using the native capabilities.

It would require a better understanding of what their reporting and sprint planning needs are, and how they currently are doing their estimation, to formulate suggestion on how they might achieve the same using the Jira functionality as it is designed to be used.


Tags: cloud

jira-cloud
Plans permission seetings for external users
Asked by Stefan Kobitsch-Meyer:

I would like to give access to Plans (just viewing) on one specific project for one external user.

What do I need to set on the permissions for this user?

Is it required to create a group first for this one user to set permission on this person?

Is it required to put this external user to the User Management User List of my company?

Important is also that this user is not allowed to see other plans or to see other projects, just for the specific project only.


Answers:
author: Walter Buggenhout
body: Hi [@Stefan Kobitsch-Meyer](/t5/user/viewprofilepage/user-id/5585933) and welcome to the Community!

If the permissions across your site have been configured properly, granting access to an external user is exactly the same as to an internal user:

* The user needs product access, as viewing data from a Jira project (even through a Plan) requires a license.
* The user needs browse project permission to the project as well.

Granting this permission is different in company managed and team managed projects, but you grant it in exactly the same way as you would for your internal users.

Coming back to the proper configuration of permissions from my first sentence: making sure that a user does not have access to any other projects than the one you specifically want to allow, obviously may have an impact on any project in your instance.

If you (or your organization) has a practice to grant browse project permissions to *any logged in user*, then this will expose all these projects to the new, external user as well as soon as he gets his Jira license and logs into your environment. This is something you will need to review across your site.

In practice, that means reviewing all *Permission Schemes* you have in use for company managed projects and replacing the *all logged in users* by a user group/project role that only contains your internal users. For team managed projects you would need to verify the permission settings for each project, making sure they are not publicly accessible.

Hope this helps!


Tags: cloud

jira-cloud

jira-software

plans
Jira to register lessons learned without Confluence
Asked by Julieta Dienstmann:

Hello Everyone,   
Does anyone has implemented a solution to use Jira as a knowledge base or a database to store lessons learned?  

What's is the problem to solve: register the lessons learned in growth experiments and make it easy for people to find it later.  
He don't have budget for jira addons or Confluence, and we'd like to avoid using Google drive and docs only.  
We'd like to customize a screen epics to register the key information about the experiment and make it easy to search for it in the future. Example: experiments about acquisition funnel that were lost.  

If you have any other idea or had the same experience, I'd love to hearing for you.  

Best,


Answers:
author: Julieta Dienstmann
body: Thank you so much, Josh! I believe this approach will be helpful. It seems like a good way to document lessons learned, but I'm curious---will it be easy to search for them using keywords? Do you have any suggestions on how to achieve that in Jira?


author: Josh Costella
body: Hi [@Julieta Dienstmann](/t5/user/viewprofilepage/user-id/4935967)

With Jira you have the flexibility to create custom issue types with any type of custom field. The only mandatory field is the Summary (title) of the issue. You could easily create a new issue type called "Learnings" (or similar) and then add whichever fields make the most sense for your findings. You can create additional custom Paragraph fields to use instead of Description. Those fields can support rich text formatting as well.

<https://support.atlassian.com/jira-cloud-administration/docs/add-edit-and-delete-an-issue-type/>

<https://support.atlassian.com/jira-cloud-administration/docs/associate-issue-types-with-projects/>

<https://support.atlassian.com/jira-cloud-administration/docs/create-a-custom-field/>

<https://support.atlassian.com/jira-cloud-administration/docs/add-a-custom-field-to-a-screen/>


Tags: cloud

confluence-cloud

jira-cloud

knowledge-base
Automating Story Creation
Asked by Amanda Crawford:

I am trying to automate the creation of stories when a multi-picker field is changed (any change) to create a story with a unique summary to match individual items in the multi-picker field.

For instance: Lines of Business - Line 1, Line 7, and line 13 are all selected.

I want multiple stories to be created with the summary Title - Line 1 and another story Title - Line 7 and another Title - Line 13. How do I do this?

Here is what I have tried:

When: Value Changes for

For Each: Lines of Business

Then: Create Issue

However, it creates as many stories as items selected (3 stories, Title - Line 1, Line 7, Line 13), but all of the items are in the summary line, instead of a summary for each item.

Thanks in Advance!


Answers:
author: Tessa Tuteleers
body: Hi [@Amanda Crawford](/t5/user/viewprofilepage/user-id/5298874) ,

welcome to the community!

Please provide a screenshot of your rule, especcially the branching / creation of issues, so we know what we are working with.

If you use smart brancing to iterate over your multi-select custom field value, and you then use the newly created variable in your branch, you should be able to use this in the creation of your new issues in the branch.

- Tessa


Tags: cloud
"Start date" / "End date" customfield timestamp logic
Asked by NIKHU:

Hi Atlassians,   

There are customfields "Start date"/ "End date" enabled in jira project. To select values for these fields Calendar Picker is used. It allows to select date but not exact timestamp, however in Jira DB these fields are stored as timestamps with a random time (correct me if I'm wrong).  
Could you please describe the logic of timestamp for these field being generated (time part of timestamp)?  
Thank you in advance!


Answers:
author: Trudy Claspill
body: Hello [@NIKHU](/t5/user/viewprofilepage/user-id/5319723)

Welcome to the Atlassian community.

How did you determine that a random time is being added to the data in the database?

If the Start date and End date fields are presenting only a Calendar for selecting a value, then they are Date Picker fields and the time information is irrelevant.

comments: author: NIKHU
body: ![p2.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/281653i8D3E460B7050C4D4/image-size/large?v=v2&px=999 "p2.PNG")![p3.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/281654iE67A71178E0F0889/image-size/large?v=v2&px=999 "p3.PNG")

With date picker user is not allowed to select time part to the value, but time is added automatically on backend side. And it is not the same for different issues (but in most cases time is set to 22:00, 23:00 or 00:00)

![p4.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/281665i61C76C706C3FF7F5/image-size/large?v=v2&px=999 "p4.PNG")![p5.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/281666iE125B9B693CE66E0/image-size/large?v=v2&px=999 "p5.PNG")

I agree that time is irrelevent for this field, but just want to fully comprehend behavior of these fields.  
Thank you!