nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Retrieving information of external tickets into a project

medini_1028038066

Dear Forum members,

I'm trying currently to access via script the JIRA tickets attached to my Checklist in medini. I would like to mark a medini Checklist Item as done, as soon as all related tickets in JIRA are closed and have a column displaying the current status of all tickets.

Does someone have experience with the access?

Thank you in advance and kind regards,

Krasimira

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1024169437

Michael, I could reproduce and it seems to be a problem in the internal task util, strange.

I adapted the tasks.js to bypass this specific problem. Find a new version attached. Please use

getStatus(taskData, "State")

as that is the variant that is working for me.

Jan

All comments

medini_1024169437

Hi Krassi,

tasks are currently annotated to elements, that means its a bit tricky to (1) get hands on them from a script and (2) get information out of them. Fortunately we have a library (as usual) to make scripting simpler by using some internal stuff we expose. Find attached the mentioned library (tasks.js) which exposes a few utilities and a sample batch script that illustrates its usage. if you plan to use this in a table (e.g. as derived profile property) you can reuse parts of that script. Please use this files as is.

Happy Scripting

Jan

medini_1035261689

Hello Jan Hello Krasimira,
first of all, thanks a lot for the script. It works most of the time. I enhanced the script to provide more information. The only issue is the "State/Status" field. I'm not able to get this information.
Script:
console.log("Summary: {0}...", getSummary(taskData,"Summary"));

console.log("Status: {0}...", getStatus(taskData));

console.log("Status: {0}...", getStatus(taskData, "State"));

console.log("State: {0}...", getStandardProperty(taskData, "State"));

console.log("Description: {0}...", getDescription(taskData, "ALM_Description"));

console.log("Priority: {0}...", getStandardProperty(taskData, "ALM_Priority"));

console.log("Created By: {0}...", getStandardProperty(taskData, "Created By"));

console.log("Created Date: {0}...", getStandardProperty(taskData, "Created Date"));
Output:
Summary: [Project][Workpackage] Do something...

Status: ...

State: ...

Description: <description remove>...

Priority: Medium...

Created By: x123456...

Created Date: 1644931955000...

Do you have any suggestion?

Thanks a lot in advance,
Michael

medini_1024169437

Hi Michael,

strange, the second line (so console.log("Status: {0}...", getStatus(taskData)); ) works for me.

One idea: launch the tool in debug mode and open the "Task Details" view (under Diagnostics).

Then drop the ticket from the Task List to that view and check what attributes it has.

Before you of course have to load the ticket to the Task List.

For m it looks like that:

Please also open the task in the task editor and see which status is shown there:

Happy Scripting

Jan

medini_1035261689

Hello Jan,

Thanks a lot for the feedback. For me it looks like following:

The task looks like following:

Is this an issue of the mapping file? Could you please provide your mapping file?

Thanks a lot,
Michael

medini_1024169437

Hi Michael,

that's strange. There is no mapping file required and in place. The values are directly from Jira.

Hm. I have no real clue why this looks and behaves so different. Which version of medini is that?

And second, which version of Jira? Is there anything useful in the lower part? typically attributes starting with attribute.jira.?

Jan

medini_1035261689

Hi Jan,
I forgot to mentioned that we use the PTC Adapter instead of the Jira Adapter. Sorry for that.
I got the following information:

Does the mapping in the help still works for PTC version 11 and later?

Thanks a lot for your help,

Michael

medini_1024169437

Ah, I see. I need to check it on my end, there should not be a difference though.

The mapping should work for any version, the fact that you can see the ticket in medini with all details is already indicating that your mapping is working.

Problem has to be somethign else.

Jan

medini_1024169437

Michael, I could reproduce and it seems to be a problem in the internal task util, strange.

I adapted the tasks.js to bypass this specific problem. Find a new version attached. Please use

getStatus(taskData, "State")

as that is the variant that is working for me.

Jan

medini_1035261689

Hi Jan, now it is working. Just a quick note:
The "var" in line 159 is missing. It should be "var attributeValue = getAttributeValue2(data, attribute);"

Regards,

Michael

medini_1024169437

Glad it works and thanks for the hint. Please mark as answered later.

Happy Scripting

Jan

medini_1035261689

Hi Jan,
How do I makr as "answered"?
Regards,
Michael

medini_1024169437

Ah, I think only Krasimira can do it (because she initiated the thread) or a forum admin . I will check.

Jan

medini_1040753747

Trying to connect medini 2021 R2 to JIRA 9... getting synchronization failures:

medini_1023909254

Hi Johan,

can you report this directly from medini using "Contact Support" from Help-menu? - this will give us more extended error logfiles and helps to investigate the issue.

Eckhardt

medini_1024169437

Johan, what exactly have you tried in terms of scripting, could you show?

Are you sure you passed a valid ticket id to the API? In JIRA the ticket ID and KEY are different things.

Id may be 123456789 but key might be "MYPROJECT-12" or so.

Jan

medini_1040753747

Hi Jan,

Not doing anything scripting wise, just trying to synchronize the tools. Looks like Bhanu responded to our IT team and is saying we have Jira set up with sub-tasks instead of tasks. So we are looking into it...

Johan

medini_1024169437

Ah, I thought you are doing what Michael was doing: he was using a script library to retrieve tickets.

Ok, so you transfered the issue to the support, good to know.

Jan

medini_1063548292

Hi all ,

I guess this means that there is no chance how to access the task through OCL using mediniGetOposites('..') on through some EObject features? I wanted to avoid configurin another pofirle property and simply use it inside of the M2DOC report together with reference link to an element -> here I expect that I can reuse the as the basic for tasks.js file with all m2doc service functions.

PS: I have also encountered similar 401 JIRA status error so I directly created Ticket with the Support team I got suspicion that it might be related to some authorization updates of Atlassian anouncement.

I will keep you update with the resolution.

Marian

medini_1024169437

Yeah, since a while get more reports on JIRA issues which worked before. Maybe Atalssian rolled out some fix/extension/feature that breaks the connector?

Not sure yet.

About the other question, Marian: please check M2Doc Sample Reports #B: Basic Services : Ansys medini analyze Support (freshdesk.com) .

There it is mentioned and shown that you can run arbitrary java script inside M2Doc so you of course should be able to access all ticket details in mdoc without creating profile properties in medini.

Happy Reporting

Jan