Artem Nek_Votazz Atlassian Partner

Comments

  • @Pratik Lodha Thank you, The rendered source is really helpful — it rules the allowlists out and points at two concrete things. 1) Images: the broken ones are unresolved Velocity, not blocked or session-auth URLs. What actually came through: avatar: src="$attachmentsManager.getAvatarUrl($actionerUser.name)" comment:…
    in [Jira 10.x] Images/icon and CSS styles not rendering in custom Velocity (.vm) email templates Comment by Artem Nek_Votazz June 9
  • @Pratik Lodha Thank you for the logs. After digging into the 10.x specifics, I'd actually steer you away from the Velocity allowlists as the cause on 10.3.5 — they probably aren't it here: • The file allowlist only applies to .vm files loaded from the filesystem. If your com/netcracker/... template is bundled inside the…
    in [Jira 10.x] Images/icon and CSS styles not rendering in custom Velocity (.vm) email templates Comment by Artem Nek_Votazz June 8
  • Hi @Pratik Lodha A few things changed in Jira 10.0 around email/Velocity that could be behind this — worth checking which one applies rather than assuming. Here's where I'd look first. The most likely candidate is the new Velocity allowlists introduced in Jira 10.0 (the main difference from 9.4.14): • a file / file-type…
    in [Jira 10.x] Images/icon and CSS styles not rendering in custom Velocity (.vm) email templates Comment by Artem Nek_Votazz June 8
  • Hi @Dharani Dharan D Short version: this is a known limitation, not a problem with your JSON. For the importer to attribute history to a real user, that user has to be defined in the top-level "users" array and the history "author" must match its "name" exactly — on Cloud that's the accountId. The official format example…
    in while uploading history using json , the user field cannot editable Comment by Artem Nek_Votazz June 8
  • @Zaki Alam Nice — that actually confirms the root cause. The duplicate users are the user-sync issue that was behind the login loop, so you've found the real thing. On the duplicates: those almost always come from your identity setup — mismatched SSO/SCIM attribute mappings (e.g. one side keying on email, the other on…
    in NREUM during login Comment by Artem Nek_Votazz June 3
  • @Gor Greyan Thanks — that's a useful clue, it definitely points at something rank- related (visibility shouldn't depend on the Ranking toggle otherwise). I just want to make sure I read the behaviour correctly, because a couple of the details seem to point in opposite directions: • With Ranking ON — is the issue visible or…
    in Issue Count Inconsistency in Backlog and In Issue Search Comment by Artem Nek_Votazz June 2
  • Without seeing the actual issues I can't say for certain, but a count like this almost always comes down to one (or both) of two well-known behaviours — the board/backlog and a raw JQL search just don't count the same way. A board's backlog only shows issues that (a) match the board's filter and (b) have that sprint as…
    in Issue Count Inconsistency in Backlog and In Issue Search Comment by Artem Nek_Votazz June 2
  • @Zaki Alam You're right — with incognito, multiple browsers, the mobile app and multiple users across locations all hitting it, this isn't client-side. The NREUM / ERR_BLOCKED_BY_CLIENT lines are just blocked telemetry, not the cause. That "database is taking a little longer than usual to sync up" screen is an…
    in NREUM during login Comment by Artem Nek_Votazz June 2
  • Hard to say for certain from the console alone, but both errors point the same way — at the client side, not Atlassian. net::ERR_BLOCKED_BY_CLIENT only happens when something on your end blocks a request (an ad blocker / privacy extension, or a network filter), never from the server. And "NREUM is not defined" means New…
    in NREUM during login Comment by Artem Nek_Votazz June 1
  • Hi Chris, A few separate things are going on here: 1) The macro doesn't take a URL by design. Include Page (the "Include content" macro in the Cloud editor) resolves its target by page title/ID through the picker, not by a pasted link — so dropping the link in won't work, even though the link itself is valid. 2) The…
    in /include doesn't find my newly created page Comment by Artem Nek_Votazz June 1
  • Hi Yatish, Good instinct to question the token — there are two recent Atlassian token changes that matter here, though one clue still narrows it down. The clue that rules most of it out: your own token — the one that works for you — also 401s for this user. A valid classic (unscoped) token works from any machine against…
    in Java application getting unauthenticated error for single user Comment by Artem Nek_Votazz June 1
  • Hi Jack, The problem is the smart value itself: daysBetween isn't a function in Jira automation, so the whole expression never resolves to a number. With the left side of your "less than 3" check blank, that first branch passes every time — which is exactly what your audit log shows. There's a single date-difference…
    in Error on Rule that Compare field Value and Set Value Comment by Artem Nek_Votazz June 1
  • Hi Samrat Short answer: no — Atlassian isn't retiring the v2 (or v3) Jira platform REST API as a whole. Both remain supported; v3 is just the ADF-aware twin of v2, not a replacement that deprecates it. What got deprecated was a specific set of endpoints — not a version. This was announced back in October 2024: • GET/POST…
    in Is Atlassian deprecating v2 APIs entirely? Comment by Artem Nek_Votazz June 1
  • Done!
    in 📝 Help shape the future of Marketplace trust Comment by Artem Nek_Votazz June 1
Avatar