A custom child headline e.g for own notes, which is not pushed to jira

[NimSed]

Hi. Thanks for this great package!
In my workflow, I use each jira ticket as a "project", as in GTD terminology, which has many sub-tasks. I'd like to be able to place these sub-tasks right under the org item containing the ticket, but still keep them private (=local, only in the org file). Right now doing so causes problems and most of the times interrupts updating/refreshing.
Is such a feature already implemented and I'm missing it? Otherwise, is there any possible workaround?

[ahungry]

I'm not sure - if anyone else is, feel free to chime in.

[LeeRuns]

CREATING SUBTASKS

Defining the Need:

Ideally, we can write under an issue in standard org notation, build-out TODO;'s, and other subheadings. This will allow all of us ORG users to write stuff down in our happy place and know that it is going to get pushed up to jira. This should also include the ability to add a "hide_subtree=True" property. This could be placed in a subtree so that the notes below it don't get pushed up to jira. This would be nice if you want to take a TON of notes but only want to load your "key notes/conclusions" to jira. Does that sound reasonable @NimSed ? TBH I would like this feature but it is not as critical as the formatting of my notes. Meaning currently the subtree gets converted out of being in org format when I push. I really really wish that it worked like this.

Scenario 0:

1. add a set of TODO, and other subtrees under TODO MyIssue0 from org-mode locally
2. hit org update issues, and all of my changes in my current org buffer update the respective jira project
3. jira tickets now have Markdown which matches the subtree
4. then anyone can edit the ticket in jira based on the markdown notation
5. when I go to "get updates" from jira the markdown is converted back into a TODO subtree

Current problem:

I create the subtree, then it inserts spaces and # syntax inside my org file. Then when i look at it on jira it looks clunky. Meaning it's just importing the raw text, not identifying the subtree as a headline, then formatting the markdown accordingly.

Inversely when I import the issue it doesn't show up as clean org-tree instead it's got a bunch of hashed lines, which require me to go back and delete spaces,hases, then org starts to see the relationship.

I really like this tool, if you need support or have a patreon page I am interested in supporting.

[NimSed]

Sorry for the very late reply.
Since I have migrated away from using sub-tasks, my notes might not be quite relevant any more. But here some recent updates:

• I just went ahead and added my "tasks" as org headings under the JIRA issues in my org file, and they seem to be OK: org-jira apparently does not try to push them to JIRA servers.
• Just a few minutes ago, I submitted this PR: Added org-jira-refresh-issues-in-buffer-loose() #300
  What it does is to allow for moving all org-jira issues to any arbitrary org file and keeping them in sync. Without this PR it is close to impossible to maintain such a configuration.

Hope this helps.

[ahungry]

The PR was merged, but I forgot to close this - thanks again for the update - closing this out.